feedburner.google.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 13:08 UTC. Grade A (96/100), with the screenshots, the timings and the fixes that matter.

https://feedburner.google.com/

20 October 2026 at 13:08 UTC · Free test · report pt_2541c8f227e5
Grade
A
96/100
Performance98/100
Structure92/100

13 audit(s) passed, 3 need work

First byte (TTFB)283 msmeasured from this server
Fully loaded787 msfirst byte + slowest asset
Requests7document + assets
Page weight396.6 KBcompressed transfer
HTML document1.3 KBno compression
ProtocolHTTP/3sffe
Third-party160.9 KBother hosts

Where the first byte went

  • DNS lookup 78 ms 28%
  • TCP connect 47 ms 17%
  • Server wait 157 ms 55%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 78% of 4,999 pages tested here283 ms against a median of 449 ms
Page weightlighter than 65% of 4,999 pages tested here396.6 KB against a median of 650.5 KB
Fully loadedfaster than 95% of 4,999 pages tested here787 ms against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte arrived in 283 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 396.6 KB over 7 request(s), which is lean. Javascript files are 97% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 41% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element painted at 444 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.009), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 111 ms in total, which is not enough to feel.

Fix first: JavaScript weight - Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of feedburner.google.com
Mobile 390 × 844 · 24.3 KB · page is 844 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint444 msgood is under 2.5 s
Cumulative layout shift0.009under 0.1 is stable
Total blocking time111 mslong tasks during load
First contentful paint388 msfirst content on screen
Browser page weight1.47 MB37 request(s), scripts included
Failed requests2blocked or unreachable
Largest contentful paint444 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.009
Goodgood under 0.1, poor over 0.25
Total blocking time111 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests
384.3 KB 97%
Css 3 requests
10.9 KB 3%

Transfer size, compressed as sent. 7 request(s) in total, 396.6 KB across all of them.

Top issues

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: js.js (224.0 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.

Waterfall

Slowest requests

JAVASCRIPTwww.googletagmanager.com/gtag/js
504 ms
CSSfeedburner.google.com/bundle/releases/2022080215/material-th…
430 ms
HTMLfeedburner.google.com/fb/images/favicon.ico
423 ms
CSSfonts.googleapis.com/css
414 ms
CSSfeedburner.google.com/bundle/releases/2022080215/css.css
411 ms
JAVASCRIPTfeedburner.google.com/bundle/releases/2022080215/js.js
381 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.googletagmanager.com/gtag/js?id=G-M8TJF03PT7 3rd partyjavascript200504 ms160.3 KB
https://feedburner.google.com/bundle/releases/2022080215/material-theme.csscss200430 ms9.9 KB
https://feedburner.google.com/fb/images/favicon.icohtml404423 ms0 B
https://fonts.googleapis.com/css?family=Roboto:300,400,500|Google+Sans:300,400,500|Oswald:300,400,500|Material+Icons 3rd partycss200414 ms562 B
https://feedburner.google.com/bundle/releases/2022080215/css.csscss200411 ms494 B
https://feedburner.google.com/bundle/releases/2022080215/js.jsjavascript200381 ms224.0 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.