hellogenie.com speed test — 20 Oct 2026

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

https://hellogenie.com/

20 October 2026 at 13:23 UTC · Free test · report pt_7eece499064b
Grade
A
97/100
Performance99/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)226 msmeasured from this server
Fully loaded675 msfirst byte + slowest asset
Requests8document + assets
Page weight137.4 KBcompressed transfer
HTML document1.0 KBgzip
ProtocolHTTP/3AmazonS3
Third-party92.3 KBother hosts

Where the first byte went

  • DNS lookup 64 ms 28%
  • TCP connect 30 ms 13%
  • Server wait 132 ms 58%

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 89% of 4,999 pages tested here226 ms against a median of 449 ms
Page weightlighter than 84% of 4,999 pages tested here137.4 KB against a median of 650.5 KB
Fully loadedfaster than 96% of 4,999 pages tested here675 ms against a median of 1.84 s
Requestssends fewer requests than 90% of 4,999 pages tested here8 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 226 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 137.4 KB over 8 request(s), which is lean. Javascript files are 74% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 67% 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 520 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.002), so nothing jumps under the reader's cursor.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

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 hellogenie.com
Mobile 390 × 844 · 39.7 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 paint520 msgood is under 2.5 s
Cumulative layout shift0.002under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint504 msfirst content on screen
Browser page weight183.0 KB11 request(s), scripts included
Largest contentful paint520 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.002
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 3 requests
101.0 KB 74%
Css 3 requests
20.3 KB 15%
Images 1 request
15.0 KB 11%

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

Top issues

Render-blocking resources

high impact

6 render-blocking resource(s) in the document head (3 script(s), 3 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

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.

Waterfall

Slowest requests

CSSfonts.googleapis.com/css
449 ms
IMAGEShellogenie.com/images/favicon.ico
428 ms
CSShellogenie.com/css/bootstrap.css
408 ms
JAVASCRIPThellogenie.com/js/bootstrap.min.js
408 ms
JAVASCRIPTajax.googleapis.com/ajax/libs/jqueryui/1.11.4/jquery-ui.mi…
378 ms
JAVASCRIPTajax.googleapis.com/ajax/libs/jquery/2.1.4/jquery.min.js
377 ms
CSShellogenie.com/css/custom.css
346 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://fonts.googleapis.com/css?family=Oswald|Source+Sans+Pro:300,400,400i,600 3rd partycss200449 ms305 B
https://hellogenie.com/images/favicon.icoimages200428 ms15.0 KB
https://hellogenie.com/css/bootstrap.csscss200408 ms18.9 KB
https://hellogenie.com/js/bootstrap.min.jsjavascript200408 ms9.0 KB
https://ajax.googleapis.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js 3rd partyjavascript200378 ms63.0 KB
https://ajax.googleapis.com/ajax/libs/jquery/2.1.4/jquery.min.js 3rd partyjavascript200377 ms29.0 KB
https://hellogenie.com/css/custom.csscss200346 ms1.1 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.