A fast homepage can still hide a slow site

Originally published at pafcore.site/a-fast-homepage-can-still-hide-a-slow-site.

A homepage score is the speed score for the home URL only. It is not a score for the whole site. I have seen a shop home sit near 88 and checkout sit near 41. Same host. Same theme. Different files. People still share the home screenshot and call the job done.

This piece is the plain version of that mistake, and a free way to check a real page with PafCore. When we can, we name the slow file.

What people feel that you miss

You live on the home page. Visitors do not.

• They tap a product and wait on a blank screen.
• They reach checkout and the first tap does nothing.
• They open a campaign page and the big picture arrives late.

Home can feel fine. The wait shows up one click later. A score on home will not warn you. I wrote about why a number on its own is thin in Why a performance score is not enough.

Why the usual tools stop at one URL

Google PageSpeed Insights checks the address you paste. One address. Lighthouse does the same. That is useful. It is also easy to misread.

People paste the home page because it is the one they remember. The report looks serious. The number is high enough. They stop. The rest of the site never gets a turn.

Each page loads its own pictures and scripts. A chat widget on a help page. A big gallery on a product page. A payment script on checkout. Home never asked for those files. So home never paid for them.

Keep it honest: a strong homepage score is still good news. It is not a pass for the site. Treat it as one page you measured, then measure the next one people use.

Pages that hide the wait

These are the ones I would open after home.

Checkout or a form. Extra scripts. Extra fields. The page that should feel sharp often feels late.

A product page or a busy post. Large pictures. Reviews. Related items. The template looks like home. The files do not.

Search results. A list that builds itself after the page opens. The first screen can sit empty.

A campaign landing page. Heavy video. Heavy animation. Built for a click, then forgotten in the speed check.

Same site. Different wait. Start with the page that costs the most points.

What a useful check does

A useful check does not stop at home.

1. Run a page more than once so you see a middle score, not one lucky screenshot.
2. Show how far the score moves on its own (the quiet gap).
3. Name the slow file when the measurement can find it.
4. Let you compare pages so the worst one is obvious.

That is what PafCore is built for. Paste a public URL. Free report. No signup. When we can see the cost, we name the file. When we cannot, we still tell you what to try first.

You can also scan a whole site. Up to 20 pages. Worst first. That pack costs 20 credits and emails you when it finishes. Start with the free one page check if you have not used credits yet.

How to check more than your homepage

1. Paste the home URL at pafcore.site. Note the middle score.
2. Open a page people actually use. Checkout. A product. A form. A busy post.
3. Paste that full address. Wait for the middle score.
4. Fix the worst page first. If a file is named, start there.

Use the live public URL. A page behind a login will not load the same way for a free public check. Start with what visitors already see. Scores also move when you change nothing. Learn that quiet gap before you celebrate. See Why your Lighthouse score changes when you did nothing.

For freelancers and agencies

Clients send a home screenshot. They ask if the site is fast. The honest answer is “I have not checked the page they pay on.”

Send two links. Home and the page that matters. Talk in plain words: what the visitor felt, which file hurt, what you will fix next. A named file is easier to explain than a long tip list. More on that split in When PageSpeed Insights is enough (and when it is not).

PafCore can carry your name on the report when white label is on. If you manage many sites and need schedules, that is Pro Watch.

FAQ

Does PageSpeed Insights check my whole website?

No. It checks one URL at a time. A homepage score is not a score for every page on the site.

Why is my homepage fast but checkout is slow?

Those pages load different files. Checkout often pulls extra scripts, forms, and pictures the home page never uses. Measure checkout on its own.

Should I only test my homepage?

No. Test the pages people actually use. Home, a product or post, and the page where they pay or send a form.

Can PafCore scan a whole site?

Yes. It can read up to 20 pages and show the worst first. That pack costs 20 credits and emails you when it finishes. A one page check is still free.