Does website speed matter? A plain guide to fast pages on a phone

Why speed matters

• Visitors. Most people look at your site on a phone, often on a mobile connection that is slower than your office wifi. If nothing appears quickly, they go back to the results and choose someone else.
• Google. Page experience, including these speed measures, is something Google looks at. It is one factor among many, and a fast page does not make up for weak content, but a very slow one can hold you back.
• AI tools and crawlers. A page that is quick and simple to load is easy to read and re-read.
• You. A fast page makes you look careful and professional before anyone reads a word.

The three measures, in plain words

Google judges these on real visits, taking the figure that three in four visits beat (the 75th percentile), separately for phones and computers. INP replaced an older measure called First Input Delay in March 2024. If your page is new or has few visitors, there may not be enough real-visit data yet, and the tools show a test result instead.

Test your page in two minutes

1. Go to PageSpeed Insights (pagespeed.web.dev) and paste your page address.
2. Wait for the report. It shows results for Mobile and Desktop; look at Mobile first.
3. At the top, check the Core Web Vitals assessment. If your page has enough real-visit data, it will say whether it passed. If not, look at the lab results below it instead.
4. Scroll to the list of opportunities and diagnostics. The ones that save the most time are at the top.
5. Note the largest items; you do not need to understand every line.
6. Test again after you change something. Results vary a little each time.

You can also simply open the page on your phone, on mobile data, with wifi switched off. If it takes more than a few seconds to show your name and photograph, it is too slow.

The five usual causes

1. Oversized photographs

This is the cause by far in most cases. A phone photograph can be 4,000 pixels wide and several megabytes, but a screen shows it at a few hundred or at most about 1,600 pixels wide. The page downloads the whole file anyway.

2. Auto-playing video and animated sliders

Videos and carousels that start by themselves are heavy and often hide the one message a visitor came for. Use a still image and a play button if you need video.

3. Too many add-ons and scripts

Chat widgets, tracking tools, booking plug-ins, social feeds and fonts each add files to download. Each may be useful; together they slow the page. Keep only the ones you really use.

4. Pop-ups and banners

Cookie banners, newsletter pop-ups and notifications that push the content down make the page jump (poor layout stability), and can cover the content on a phone. Google also advises against intrusive pop-ups that cover content.

5. Slow hosting or a heavy theme

A cheap or overloaded hosting plan, or a theme loaded with features you never use, adds delay before anything arrives. A simple, purpose-built page avoids both.

How to fix photographs, step by step

1. Decide how large each photograph will appear. A full-width photograph on a phone needs about 800 to 1,200 pixels across; on a large screen, about 1,600. A small portrait needs only a few hundred.
2. Resize it to that size before uploading. Free tools such as Squoosh (squoosh.app) and TinyPNG do this in a browser, and your phone’s photo app can resize too.
3. Choose a modern format if your tool allows it. WebP and AVIF are usually much smaller than JPEG for the same quality; JPEG is fine if you compress it.
4. Compress it until it looks right. For a hero photograph, a few hundred kilobytes is a sensible target; for a small image, tens of kilobytes. These are rules of thumb, not requirements.
5. Give every image a short description (alt text), which helps people using screen readers and search engines.
6. Do not upload the same large photograph for the thumbnail and the full picture.

Other fixes anyone can make

• Cut the number of fonts and weights. One or two is enough.
• Remove add-ons and scripts you do not use, and check each remaining one is worth its cost.
• Replace carousels with a single strong image and message.
• Make sure image sizes are set, so that the layout does not jump when they load. Good builders do this for you.
• Delay anything below the first screen, such as a map or video, until the visitor scrolls to it (called lazy loading). Many builders have a switch for it.
• Use a simple layout. Fewer sections and elements are quicker.
• Keep your page short. One page with a few compressed photographs is easy to keep fast.

What a good result looks like

For a professional’s page, a good target is the main content appearing in about two seconds on a normal mobile connection, tapping a button responding at once, and nothing jumping. You do not need a perfect 100 score in a test tool. A score is a guide, not the goal; what matters is that real visitors on real phones can read and act quickly.

Common mistakes

• Chasing a perfect score and breaking the page to get it.
• Testing only on a fast office connection and a computer.
• Uploading original phone photographs untouched.
• Adding a new widget without testing before and after.
• Ignoring the Mobile tab.
• Treating speed as a one-off. Test whenever you add something.

How BeVisible helps

BeVisible pages are a single, simple page, built to load quickly on a phone, with no heavy theme or add-ons. Photographs are shrunk in your browser when you upload them and saved in a small and a large version (WebP or JPEG), so visitors’ phones download the small one. A video loads only when a visitor taps play, and there are no sliders or carousels. You can build and preview free, and publish free for 7 days with no card needed; after that one yearly plan keeps a website online, and one plan covers one website. Start from a photo or type your details.