www.e-planning.net speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 15:20 UTC. Grade D (66/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 58 ms 14%
- TCP connect 97 ms 24%
- Server wait 245 ms 61%
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
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 401 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 3.73 MB over 26 request(s). Images files are 94% of it, so resize and recompress the largest images before anything else.
- The HTML itself arrives gzip-compressed.
- It runs over HTTP/2, so the assets share a connection instead of opening one each.
- The largest element painted at 1.06 s, inside the 2.5 s Google calls good.
- Layout shift is 0.105 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
- The main thread was blocked for 764 ms, so taps and scrolling wait while scripts run.
Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.
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.
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.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 26 request(s) in total, 3.73 MB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 401 ms. Of that, 245 ms was the server thinking and 155 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.
Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.
Image delivery and format
high impact4 image(s) over 200 KB and 4 large image(s) still served as JPEG or PNG.
Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.
Render-blocking resources
high impact8 render-blocking resource(s) in the document head (1 script(s), 7 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.
Total page weight
high impactThe page transfers 3.73 MB across 26 request(s), with the document itself at 4.5 KB.
Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.
Cache static assets
medium impact19 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.
Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.
Waterfall
Slowest requests
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
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| https://kit.fontawesome.com/83fb5e9160.js 3rd party | javascript | 403 | 1.05 s | 9 B |
| https://www.e-planning.net/images/mike-glover.jpeg | images | 200 | 1.02 s | 82.3 KB |
| https://www.e-planning.net/images/ian.jpg | images | 200 | 1.02 s | 986.7 KB |
| https://www.e-planning.net/images/Tele.png | images | 200 | 1.02 s | 715.8 KB |
| https://www.e-planning.net/images/Celular.png | images | 200 | 1.02 s | 937.6 KB |
| https://www.e-planning.net/images/Web.png | images | 200 | 1.01 s | 529.8 KB |
| https://www.e-planning.net/images/implementation.png | images | 200 | 1.01 s | 18.7 KB |
| https://www.e-planning.net/images/quality.png | images | 200 | 1.01 s | 27.5 KB |
| https://www.e-planning.net/images/Yahoo-logo-1.png | images | 200 | 1.01 s | 10.5 KB |
| https://www.e-planning.net/images/lorenzo-nicodemo.jpeg | images | 200 | 1.01 s | 35.1 KB |
| https://www.e-planning.net/img/bar-graph.svg | images | 200 | 1.01 s | 8.7 KB |
| https://www.e-planning.net/images/Lotame_Logo-1200x229.png | images | 200 | 1.00 s | 75.4 KB |
| https://www.e-planning.net/images/sebastian-lotame.jpeg | images | 200 | 1.00 s | 94.8 KB |
| https://www.e-planning.net/images/basis.jpg | images | 200 | 996 ms | 12.6 KB |
| https://www.e-planning.net/scripts/index.js | javascript | 200 | 995 ms | 419 B |
| https://www.e-planning.net/images/datacenter.png | images | 200 | 990 ms | 23.8 KB |
| https://www.e-planning.net/images/exclusivedemand.png | images | 200 | 985 ms | 12.0 KB |
| https://www.e-planning.net/img/handshake.svg | images | 200 | 982 ms | 7.1 KB |
| https://www.e-planning.net/styles/header.css | css | 200 | 982 ms | 1.0 KB |
| https://www.e-planning.net/scripts/header.js | javascript | 200 | 970 ms | 1.6 KB |
| https://cdnjs.cloudflare.com/ajax/libs/OwlCarousel2/2.3.4/owl.carousel.min.js 3rd party | javascript | 200 | 964 ms | 9.9 KB |
| https://js.hsforms.net/forms/embed/v2.js 3rd party | javascript | 200 | 933 ms | 196.1 KB |
| https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.0/jquery.min.js 3rd party | javascript | 200 | 933 ms | 27.3 KB |
| https://js.hs-scripts.com/43954328.js 3rd party | javascript | 200 | 933 ms | 741 B |
| https://www.e-planning.net/./images/logo verve group.png | images | 0 | 0 ms | 0 B |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.