8.2 sec in total
1.5 sec
6.5 sec
194 ms
Click here to check amazing Stats content for Saudi Arabia. Otherwise, check out these important facts you probably never knew about stats.gov.sa
نحن هنا لنكون المرجع الإحصائي الأكثر تميزًا وابتكاراً لدعم التنمية الاقتصادية والاجتماعية في #السعودية
Visit stats.gov.saWe analyzed Stats.gov.sa page load time and found that the first response time was 1.5 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
stats.gov.sa performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value11.6 s
0/100
25%
Value20.6 s
0/100
10%
Value70 ms
99/100
30%
Value0.156
74/100
15%
Value12.1 s
16/100
10%
1490 ms
333 ms
349 ms
353 ms
15 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 69% of them (60 requests) were addressed to the original Stats.gov.sa, 5% (4 requests) were made to Cm.g.doubleclick.net and 3% (3 requests) were made to W.sharethis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Stats.gov.sa.
Page size can be reduced by 1.4 MB (65%)
2.2 MB
750.3 kB
In fact, the total size of Stats.gov.sa main page is 2.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 114.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 32.5 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 114.8 kB or 89% of the original size.
Potential reduce by 52.4 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Stats needs image optimization as it can save up to 52.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 856.8 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 856.8 kB or 78% of the original size.
Potential reduce by 386.7 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Stats.gov.sa needs all CSS files to be minified and compressed as it can save up to 386.7 kB or 84% of the original size.
Number of requests can be reduced by 25 (32%)
78
53
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stats. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
stats.gov.sa
1490 ms
css_1IPY1A8ooBlfDk0A39LbR7mqwp8b5PoaQGUN-oYphbw.css
333 ms
css_aokCpVyhqWz4GLkkES-wKybgp9dBnmBQJl44cB3xevI.css
349 ms
css_UZKQHq62HOKE70JDIdMjjfRn1JIC9YV1VXhRL-j6-RM.css
353 ms
bootstrap.min.css
15 ms
css_vVRFOWlWYQYG5muW_wDJtnjWXtzyBK1ol33X0HC-4ac.css
523 ms
bootstrap-rtl.min.css
550 ms
custome-rtl.css
386 ms
style-rtl.css
674 ms
js_MpKfe1sTh5JIVGCZ17DsAuT1rqAC38MLLlkjqjQ1X_k.js
896 ms
bootstrap.min.js
11 ms
js_AL6ySQOiD8AW7Ra0Jl9G0i8CVnJsXrVxBw03RJ13xvg.js
711 ms
js_lICp2NZsr5GP9kfyGZhEWFcZvNuj8p9Zerd6lmaDFk8.js
1631 ms
buttons.js
7 ms
js_L50O_PWoAuMOxVjnzZCkNSSmI0kFwhZsO1_KS8WnGKw.js
842 ms
analytics.js
7 ms
collect
14 ms
collect
68 ms
collect
23 ms
stats_logo_ar.png
270 ms
jmly_dd_lskn_lm_2014_nsm1_copy.PNG
358 ms
%D9%86%D9%85%D9%88%20%D8%A7%D9%84%D8%B5%D8%A7%D8%AF%D8%B1%D8%A7%D8%AA%20%D8%A7%D9%84%D8%B3%D9%84%D8%B9%D9%8A%D8%A9.png
358 ms
mdl_lltHq_ljmly_bltlym_lbtdyy_2014.png
359 ms
mdl_lltHq_lSfy_bltlym_lbtdyy_2014.png
360 ms
mdl_wfyt_lTfl_lrD_lkl_lf_mwlwd_Hy_2014.png
377 ms
mdl_lmshrk_lqtSdy_lmnqH_llswdyyn_2014.png
514 ms
nsb_lskn_lmlyn_l_dd_lskn_2014.png
696 ms
mdl_lbTl_llswdyyn_15_sn_fkthr_2014.png
707 ms
mdl_lbTl_ljmly_lskn_15_sn_fkthr_2014.png
717 ms
ltGyr_fy_lrqm_lqysy_ltklf_lmysh_ltDkhm_2014.png
717 ms
lrqm_lqysy_lm_ltklf_lmysh_2014.png
736 ms
mshm_lSdrt_fy_lntj_lmHly_ljmly_lm_2015_blsr_ljry.png
850 ms
nmw_lwrdt_lsly_blsr_ljry_lm_2015.png
1053 ms
nmw_lSdrt_lsly.png
1041 ms
mwshrt_ltnw_lqtSdy_0.png
1052 ms
mshm_lSdrt_fy_lntj_lmHly_ljmly_lm_2015_blsr_ljry_0.png
1053 ms
nSyb_lfrd_mn_lntj_lmHly_ljmly_lm_2015_blsr_ljry.png
1078 ms
nmw_lntj_lmHly_ljmly_blsr_lthbt.png
1205 ms
mdl_nmw_lskn_lswdyyn_lm.png
1388 ms
dd_lskn_lswdyyn_lm_2014.png
1396 ms
lkthf_lskny_frd-km_mrb_lm_2014.png
1406 ms
mdl_nmw_lskn_lm_2014.png
1406 ms
%D8%B3%D9%84%D8%A7%D9%8A%D8%AF%D8%B1%20%D8%A7%D9%84%D8%AA%D8%B9%D8%AF%D8%A7%D8%AF%20%D8%A7%D9%84%D8%B2%D8%B1%D8%A7%D8%B9%D9%8A_0.JPG
1597 ms
4_0.jpg
1717 ms
3.jpg
1902 ms
2.jpg
1912 ms
1_3.JPG
1925 ms
icon-1c.png
1765 ms
icon-2c.png
1963 ms
icon-6c.png
2076 ms
icon-3.png
2111 ms
icon-4.png
2262 ms
icon-5.png
2259 ms
10.jpg
2256 ms
9.jpg
2292 ms
getAllAppDefault.esi
28 ms
NeoSansArabic.woff
2736 ms
getSegment.php
30 ms
checkOAuth.esi
31 ms
t.dhj
36 ms
fontawesome-webfont.woff
2453 ms
UniversNextArabic-Regular.woff
2600 ms
4_1.jpg
2258 ms
1_0.jpg
2251 ms
5_1.jpg
2283 ms
t.dhj
22 ms
x35248
132 ms
s-3271.xgi
33 ms
pixel
34 ms
hbpix
38 ms
17 ms
16 ms
pixel
33 ms
pixel
22 ms
xrefid.xgi
18 ms
pixel
33 ms
cm
13 ms
8_0.jpg
2446 ms
2981
29 ms
7_1.jpg
2283 ms
3_2.jpg
2312 ms
6_0.jpg
2455 ms
1_4.jpg
2571 ms
StatsLogo.jpg
2582 ms
index.a8fc48294ca4cc10eb440189d9f22d7c.html
11 ms
buttons.ab966a004186897711de4a5ed256c924.css
7 ms
st.125da8bfe70ad3e00a35a6e4c65d8bc5.js
4 ms
stats.gov.sa accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
stats.gov.sa best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
stats.gov.sa SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
AR
AR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stats.gov.sa can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and it matches the claimed language. Our system also found out that Stats.gov.sa main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
stats.gov.sa
Open Graph description is not detected on the main page of Stats. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: