Showcase · a site I run
Globoost: phone speed 60 to 89 in one evening
Globoost is this site. On October 16 I ran the same check I run for makers on it, on phone, tablet, desktop and iPhone Safari. The phone result was worse than I expected, so I fixed what it found and measured again.
What the check found
| Cause | What it did | Fix |
|---|---|---|
| Fade-in on the first screen | The main text faded in with a scroll effect, so it stayed invisible for about 2.3 seconds after the page had loaded. | Removed the effect from the six elements on the first screen. Lower sections keep it. |
| Font that blocks the page | The browser waited for the Google font file before drawing anything, about 1.5 seconds on slow 4G. | Draw with the system font first and switch only if the font arrives quickly. |
| Ad pixel for everyone | The Meta pixel loaded for every visitor, though only ad visitors need it. | Load it only for visitors who arrive from an ad. |
Before and after
| Before | After | |
|---|---|---|
| Google phone score | 60 | 89 |
| Main content shown (phone) | 5.8 s | 2.6 s |
| Page blocked (phone) | 550 ms | 220 ms |
| Google desktop score | not measured | 91 |
Google PageSpeed Insights, phone setting (a mid-range phone on slow 4G), October 16, 2026. It is a lab test, not a measurement on one specific phone model. The automated pass in a real browser then found the headline shifting slightly when the font arrived late; that was fixed the same evening by keeping the system font in that case.
Why it matters
On a phone, most people decide in the first few seconds. Ads were bringing visitors who left in under half a second, and an empty first screen was part of the reason. None of these fixes changed what the page says. They only changed when it shows up.