GoDesign Technologies

Practical · 7 min read

Two small jobs worth doing properly

Two unglamorous tasks with effects out of proportion to their size: compressing images properly, and converting data without opening it in a spreadsheet first.

Updated 1 September 2026 · GoDesign build team

A set of brass weighing scales on a pale sage desk, a large stone on one pan and several small ones on the other

The short version

  • Oversized images are the most common single cause of a slow page, and the easiest to fix.
  • Resize before you compress. A 4000-pixel photo compressed hard is still a 4000-pixel photo.
  • Modern formats give roughly a third off at the same visual quality, for one conversion step.
  • Data exports fed through a spreadsheet lose leading zeros, mangle dates and silently corrupt long numbers.

Two tasks that nobody enjoys and that repay attention out of all proportion to how long they take. Neither is interesting. Both are among the highest-return twenty minutes available on a typical site.

Images: the most common cause of a slow site

Page speed advice tends toward the technical — caching layers, script loading, server response times. All of it matters and none of it matters as much as the fact that most slow pages are slow because somebody uploaded a photograph straight off a camera or phone.

A modern phone produces images several thousand pixels wide and several megabytes in size. Displayed in a column eight hundred pixels wide, the browser downloads the whole thing and then throws most of it away. On a good connection this is invisible. On a phone, on mobile data, it is the entire experience.

StepTypical effect
Resize to the largest size actually displayedThe largest single saving, usually by far
Compress at a sensible qualitySubstantial, and visually indistinguishable
Convert to a modern formatRoughly a third again at the same quality
Set width and height in the markupNo size saving, but stops the page jumping as it loads

The order matters. Compressing hard without resizing is the common mistake: it degrades visible quality while leaving the fundamental problem, which is that the file describes far more pixels than anyone will see.

The fourth row in the table is worth its own mention because it fixes a different problem. Without stated dimensions, the browser does not know how much room to leave, so the page reflows as each image arrives — which is the effect where you go to tap something and it moves. It is measured as a ranking signal, and more to the point it is genuinely irritating.

Two printed photographs of identical appearance side by side on pale sage, one thick and one very thin in cross-section
Same image, same apparent quality. One of them is a third of the size, and the difference is a single conversion step.

Data: what a spreadsheet does to an export

The second job is converting structured data — an export from one system into a format another system can import. The usual approach is to open it in a spreadsheet, tidy it, and save it out again. That step is where the damage happens, silently.

  • Leading zeros disappear. Postcodes, product codes and phone numbers become numbers, and the zeros are gone before you notice.
  • Dates get reinterpreted according to local convention, so the same file means different things depending on who opened it.
  • Long identifiers become scientific notation, which is not a display quirk — it destroys the value.
  • Anything resembling a formula gets evaluated. A field starting with an equals sign is a genuine security consideration as well as a data one.

None of these produce an error. The file saves cleanly, imports cleanly, and the problems surface weeks later as records that do not match, orders that cannot be found, and a customer whose phone number has one digit fewer than it should.

The fix is to convert directly between formats without a spreadsheet in the middle. Where a spreadsheet is genuinely needed, import the file rather than opening it, and set every column that is not arithmetic to text before the data is parsed.

Why these two together

They share a shape. Both are small, both are boring, both are usually delegated to whoever has a spare moment, and both fail silently in ways that are much more expensive to discover later than to prevent now. A site that is slow on mobile and a database with corrupted identifiers are each the accumulated result of a hundred small decisions nobody thought worth attention.

Questions people ask

Why is my website slow to load on mobile?

Most often because images are far larger than the space they are displayed in. A phone photograph is several thousand pixels wide and several megabytes; shown in an 800-pixel column, the browser downloads all of it and discards most. On a fast connection this is invisible, and on mobile data it is the entire experience.

Should I resize or compress images?

Resize first, then compress. Compressing hard without resizing is the common mistake — it degrades visible quality while leaving the real problem, which is a file describing far more pixels than any display will show. As a rule of thumb, nothing needs to be wider than about twice the space it occupies.

Is WebP worth converting to?

It gives roughly a third off at the same visual quality for one conversion step, and support is effectively universal now. It is worth doing after resizing and compressing rather than instead of them, since those two account for the larger savings.

Why do my exported CSV files get corrupted?

Usually because they were opened in a spreadsheet. Leading zeros vanish from postcodes and product codes, dates get reinterpreted by local convention, long identifiers become scientific notation, and anything starting with an equals sign is evaluated as a formula. None of it errors — the problems surface weeks later as records that will not match.

How do I convert data safely?

Convert directly between formats without a spreadsheet in the middle. Where one is genuinely needed, import the file rather than opening it, and set every column that is not doing arithmetic to text before the data is parsed — after it is parsed, the damage is already done.

Built by GoDesign FZE, who build WhatsApp and CRM automation for UAE businesses.

Get in touch

Want someone to just do this part?

The tool is free and stays free. If you would rather hand the work over, tell us what you are dealing with and you get a straight answer on scope, cost and timeline.

  • You own everythingRepository, hosting and domain credentials sit in your name from day one, not handed over at the end.
  • A written timelineMilestone dates are agreed in writing before work starts, so you always know what ships next.
  • One business dayEvery enquiry gets a reply from the person who would scope the work, not a sales sequence.
scale@godesign.ae+971 58 903 1983, WhatsApp enabled

Media City, Dubai, UAE · DHA Phase 2, Islamabad, Pakistan

One reply from the person who would do the work, within one business day. Your details stay with GoDesign FZE and are never sold or passed on.

Would rather type than fill in a form?

Message on WhatsApp