When is the Right Time to Think about Web Performance?

rfp-robotRFP ROBOT: Website Request for Proposal Generator

The time has come for a new website (or website redesign), which means you need to write a website request for proposal or web RFP. A Google search produces a few examples, but they vary wildly and don’t seem to speak really to your goals for developing or redesigning a new website. You need to write a website RFP that will clearly articulate your needs and generate responses from the best website designers and developers out there. But how?

Have no fear, RFP Robot is here. He will walk you through a step-by-step process to help you work through the details of your project and create a PDF formatted website design RFP that will provide the information vendors need to write an accurate bid. RFP Robot will tell you what info you should include, point out pitfalls, and give examples.

Web performance is vital, but lately I’ve felt that the topic has only been brought up by front-end developers, and only becomes a point of discussion at the end of a project. Subsequently, whenever I hear about solutions to trim down large websites, I can’t help but feel that these are merely suggestions or tricks that developers and engineers should employ after the initial design process has kicked off.

So what sort of design topics impact performance? Well, any question that a designer might ask themselves. Like these:

How many fonts should we use?
What sort of imagery should we apply?
What kind of analytics scripts do we need?
How does a user scroll through our app?
How does this complex component affect our CSS?
How should we even write CSS?
What kind of frameworks should we choose?

More often than not, these questions will lead to more code, more complexity and more bloat in a design system since…

The more fonts we add the longer we ask our users to wait.
The type of imagery we choose for a project will impact what image formats we use.
If we pick a crazy number of analytics tools then that can slow the whole app down, too.
Adding a complex component in CSS, that will only be used once in the app, will lead to code bloat and it’ll further slow down the time to first render (if only marginally).
Deciding which framework we use will have an enormous impact on the critical path.

In short, design teams should measure their success against key web performance metrics because every decision they make will eventually lead to drastic changes in what gets sent down the pipe to the end user.
And the way I’ve started to think about it is like this: every conversation about design is also a conversation about web performance. I try to remind myself that the two are inseparable from the other and so as a Drupal Web Designer I ought to be considerate of these problems from the very beginning of a project, not just at the end.

When is the Right Time to Think about Web Performance? is a post from CSS-Tricks
Source: CssTricks

Posted on August 31, 2016 in drupal agencies, drupal agency dallas, drupal agency dfw, drupal agency houston, drupal agency san antonio, Drupal Best Practices, Drupal Blocks, Drupal COPE, drupal crisis, Drupal design college station, drupal design San Antonio, drupal design,, drupal Designer, Drupal Designer Chicago, drupal developer,, drupal developers,, Drupal Development, Drupal Development Chicago IL, Drupal Development Chicago Illinois, drupal development company,, drupal ecommerce,, Drupal Educational, drupal emergency, Drupal Entities, Drupal Experts Chicago, drupal help, Drupal in Austin, Drupal Jobs, Drupal Maintenance Austin, Drupal Maintenance Chicago, Drupal Maintenance Chicago IL

Share the Story

Back to Top