Watch a related explainer
In plain English
Page speed is the pace at which a page becomes usable after someone opens it. Picture a shop door: it is not enough for it to swing open quickly if the lights take ages to come on or the counter keeps moving. On a website, the text and main image should appear promptly, controls should respond and the layout should not jump around as files arrive.
There is no single number that describes every visitor’s experience. A phone on mobile data may behave differently from a desktop on a fast connection. A first visit may need to download more files than a return visit. Web Vitals guidance therefore looks at several aspects of the experience, including loading, interaction and visual stability. The current Core Web Vitals are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
Speed tools are useful, but their scores need context. A laboratory test can reproduce a set of conditions and suggest fixes. Field data, when available, reflects visits from real users. Neither replaces opening the site yourself and completing the task a customer came to do.
Why it matters to a Jersey business
Someone looking up opening hours, a menu or a trades business number may be standing outside, travelling or using mobile data. A heavy page can delay the one fact they need. A slow form can also leave a visitor unsure whether an enquiry was sent. This is a usability issue before it is an SEO issue.
For a small local site, speed work often starts with ordinary choices: resize photographs for where they appear, avoid loading videos before they are needed, keep fonts and scripts under control, and choose hosting that serves pages reliably. Do not remove useful information simply to chase a tool score. The goal is to deliver the right content quickly and keep the site easy to use.
Google’s developer guidance recommends sites that are secure, fast, accessible and work across devices. That is a useful checklist, not a promise of a particular ranking if a number improves.
A Jersey example
Imagine a St Ouen café whose menu page starts with several full-size photographs. A person on a phone may see a blank area while the images download, even though all they want is today’s menu and the phone number. The café could keep the photographs, resize them for the display and put the key information in text near the top. The page would still look welcoming while becoming useful sooner.
This is a hypothetical example. A real diagnosis would inspect the actual page. If the server response is the main delay, changing image size alone will not solve it. If a booking widget responds slowly, the booking path needs separate attention.
What to do
Test your homepage and the pages that lead to enquiries or sales, especially on a phone. Try them on mobile data as well as Wi-Fi. Use a performance tool to identify the largest files and slow interactions, then fix one cause at a time. Web.dev’s measurement guide explains the difference between development tests and real-user measurements.
Prioritise the visible task. Can the visitor read the service, tap the number, use the menu and submit the form without waiting or fighting a shifting layout? Recheck after adding a gallery, tracking script or new widget; performance can change over time. Our short video below covers practical fixes for a small business website.
Common myths
A high score means the site feels fast to everyone. Test conditions and devices vary. Real users can still encounter a slow form or delayed third-party widget.
Speed is only an SEO concern. It affects whether customers can get information and finish a task comfortably.
Removing every image is the answer. Relevant images can help customers. Serve them at sensible sizes and load them at the right time.
Our take
Jersey Web’s view is to fix the delay a customer actually feels first. A page that shows its important information promptly and responds to taps is more useful than one built solely to maximise a score. Recheck speed whenever the site gains new media or scripts.
A real Jersey example
Choose a useful file size and loading priority
This beach photograph sits below the main explanation, so it uses lazy loading. The exports below show the actual transfer sizes of the available files. A prominent image at the top of a page needs a separate loading decision. File size helps explain part of the work involved, but it does not measure the complete page experience.
Actual delivery files
| Pixels | File size | Preview |
|---|---|---|
| 480 × 360 px | 14.6 KiB | Open 480 px export |
| 960 × 720 px | 66.2 KiB | Open 960 px export |
| 1600 × 1200 px | 200.9 KiB | Open 1600 px export |
| 1920 × 1440 px | 289.4 KiB | Open 1920 px export |
These are delivered file sizes, not a prediction of loading time or a like-for-like format benchmark.
The loading instruction used here
loading="lazy" with explicit width and height preserves the photograph’s aspect ratio while the browser decides when to load it.
Browse the original Jersey photo library → · Check photo usage terms
See it in a diagram
A smaller file is useful when the delivered image remains clear and usable.
Read the diagram in text
- Keep a master. Retain original artwork for later editing and create separate web exports.
- Choose dimensions. Prepare suitable sizes and crops for the image’s role in the layout.
- Compare exports. Review format, quality and file size. Inspect lettering and important detail.
- Verify delivery. Check the actual page files and provide useful accessible descriptions.
Related terms
Learn more
Common questions
- Is page speed just the time until a page finishes loading?
- No. A page can show useful content before every file finishes, or appear complete while a button still responds slowly. Look at the experience as well as the total load time.
- What are Core Web Vitals?
- They are Google's measures of loading, responsiveness and visual stability: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. They are useful signals, not the whole experience.
- Will a perfect speed score guarantee better rankings?
- No. Performance is one part of a useful website, and a tool score depends on the test conditions. Good content, relevant pages and working contact routes still matter.
- What should I fix first on a slow page?
- Start with the biggest visible problem, often an oversized image, unnecessary script or sluggish hosting response. Test again after each change and make sure the page still works.
Written by Jersey Web. Last reviewed 12 October 2026. Back to the Jargon Buster.