www.moe.gov.sa/ar/pages/default.aspx speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 15:35 UTC. Grade D (66/100), with the screenshots, the timings and the fixes that matter.

https://www.moe.gov.sa/ar/pages/default.aspx

20 October 2026 at 15:35 UTC · Free test · report pt_56ec4a907c31

Re-test this page Test your own site

Grade

66/100

Performance56/100

Structure80/100

13 audit(s) passed, 3 need work

First byte (TTFB)1.50 smeasured from this server

Fully loaded3.95 sfirst byte + slowest asset

Requests26document + assets

Page weight437.7 KBcompressed transfer

HTML document16.0 KBgzip

ProtocolHTTP/3server not sent

Third-party134.3 KBother hosts

Where the first byte went

DNS lookup 295 ms 20%
TCP connect 283 ms 19%
Server wait 924 ms 62%

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 byteslower than 95% of 4,999 pages tested here1.50 s against a median of 448 ms

Page weightlighter than 63% of 4,999 pages tested here437.7 KB against a median of 650.5 KB

Fully loadedslower than 88% of 4,999 pages tested here3.95 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 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 took 1.50 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 437.7 KB over 26 request(s). Html files are 66% of it, so that one type is worth a look on its own.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
31% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Html 18 requests

287.5 KB 66%

Javascript 3 requests

134.2 KB 31%

Other 1 request

31 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1502 ms. Of that, 924 ms was the server thinking and 578 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.

Render-blocking resources

high impact

8 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.

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.