11.4 sec in total
4.2 sec
7.1 sec
232 ms
Click here to check amazing Cpf content. Otherwise, check out these important facts you probably never knew about cpf.org.sa
Visit cpf.org.saWe analyzed Cpf.org.sa page load time and found that the first response time was 4.2 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
cpf.org.sa performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value2.8 s
84/100
25%
Value2.4 s
98/100
10%
Value80 ms
99/100
30%
Value0.053
98/100
15%
Value2.6 s
98/100
10%
4156 ms
252 ms
108 ms
336 ms
299 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 96% of them (112 requests) were addressed to the original Cpf.org.sa, 2% (2 requests) were made to S7.addthis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Cpf.org.sa.
Page size can be reduced by 602.5 kB (61%)
990.2 kB
387.7 kB
In fact, the total size of Cpf.org.sa main page is 990.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 588.8 kB which makes up the majority of the site volume.
Potential reduce by 98.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 98.9 kB or 76% of the original size.
Potential reduce by 62.5 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, Cpf needs image optimization as it can save up to 62.5 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 385.2 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 385.2 kB or 65% of the original size.
Potential reduce by 55.8 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. Cpf.org.sa needs all CSS files to be minified and compressed as it can save up to 55.8 kB or 87% of the original size.
Number of requests can be reduced by 12 (12%)
102
90
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cpf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
cpf.org.sa
4156 ms
default.aspx
252 ms
NoIEActivate.js
108 ms
jquery-1.4.2.min.js
336 ms
jquery.bubblepopup.min.js
299 ms
highslide.js
454 ms
highslide.css
168 ms
default.css
214 ms
jquery.bubblepopup.css
228 ms
WebResource.axd
198 ms
ScriptResource.axd
209 ms
ScriptResource.axd
326 ms
ScriptResource.axd
252 ms
addthis_widget.js
13 ms
mbScrollable.js
316 ms
swfobject.js
323 ms
bg.jpg
236 ms
spacer.gif
57 ms
spacer.gif
59 ms
Rohamaa_01.gif
181 ms
R2.gif
203 ms
Items_644.png
160 ms
Items_534.gif
180 ms
Items_458.jpg
204 ms
Items_457.jpg
305 ms
Items_456.jpg
283 ms
newsMarqueLogo.png
266 ms
MakeThumbnail.aspx
751 ms
MakeThumbnail.aspx
267 ms
MakeThumbnail.aspx
281 ms
MakeThumbnail.aspx
322 ms
MakeThumbnail.aspx
807 ms
MakeThumbnail.aspx
1312 ms
MakeThumbnail.aspx
339 ms
pdf.gif
337 ms
ppt.gif
360 ms
Volunteer.gif
366 ms
FooterText.gif
380 ms
Home_01_sliced_04.gif
394 ms
Home_01_sliced_06.gif
392 ms
Home_01_sliced_08.gif
400 ms
Home_01_sliced_10.gif
425 ms
Home_01_sliced_12.gif
548 ms
Home_01_sliced_14.gif
547 ms
Home_01_sliced_16.gif
448 ms
Home_01_sliced_18.gif
470 ms
Home_01_sliced_20.gif
492 ms
Home_01_sliced_22.gif
514 ms
ABSHeader.jpg
585 ms
bodypattern.gif
584 ms
Home_01_sliced_58.gif
582 ms
Home_01_sliced_59.gif
619 ms
Home_01_sliced_20-76.gif
619 ms
Home_01_sliced_77.gif
618 ms
ga.js
36 ms
300lo.json
37 ms
sh.8e5f85691f9aaa082472a194.html
28 ms
__utm.gif
19 ms
Home_01_sliced_79.gif
547 ms
Home_01_sliced_26-99.gif
561 ms
vote_btn.gif
559 ms
prevvote_btn.gif
548 ms
Home_01_sliced_147.gif
560 ms
Home_01_sliced_161.gif
557 ms
counterbox.gif
589 ms
welcomenotebg.jpg
560 ms
Home_01_sliced_33-66.gif
579 ms
Home_01_sliced_86.gif
571 ms
Home_01_sliced_51-84.gif
551 ms
Home_01_sliced_135.gif
536 ms
Home_01_sliced_134.gif
542 ms
Home_01_sliced_108-141.gif
561 ms
Home_01_sliced_148.gif
522 ms
morebut.gif
538 ms
Home_01_sliced_182.gif
524 ms
Home_01_sliced_152-185.gif
500 ms
enjazaitembg.gif
506 ms
Home_01_sliced_188.gif
507 ms
Home_01_sliced_205.gif
499 ms
pagermore.gif
461 ms
pagerleft.gif
474 ms
Home_01_sliced_176.gif
480 ms
Home_01_sliced_242.gif
452 ms
MakeThumbnail.aspx
395 ms
playicon.png
426 ms
MakeThumbnail.aspx
356 ms
MakeThumbnail.aspx
854 ms
MakeThumbnail.aspx
374 ms
MakeThumbnail.aspx
350 ms
MakeThumbnail.aspx
352 ms
MakeThumbnail.aspx
348 ms
MakeThumbnail.aspx
317 ms
MakeThumbnail.aspx
309 ms
MakeThumbnail.aspx
306 ms
MakeThumbnail.aspx
300 ms
MakeThumbnail.aspx
346 ms
MakeThumbnail.aspx
1403 ms
MakeThumbnail.aspx
841 ms
MakeThumbnail.aspx
293 ms
Home_01_sliced_230.gif
292 ms
dateboxbg.gif
268 ms
Home_01_sliced_37-82.gif
295 ms
Home_01_sliced_115.gif
294 ms
Home_01_sliced_62.gif
316 ms
Home_01_sliced_144.gif
316 ms
Home_01_sliced_154.gif
321 ms
Home_01_sliced_159.gif
321 ms
Home_01_sliced_168.gif
355 ms
Home_01_sliced_197.gif
373 ms
Home_01_sliced_92-216.gif
381 ms
Home_01_sliced_219.gif
393 ms
footerright.gif
401 ms
footerpattern.gif
403 ms
footerleft.gif
408 ms
rounded-white.png
54 ms
zoomout.cur
36 ms
loader.white.gif
33 ms
cpf.org.sa accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
cpf.org.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
cpf.org.sa SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
AR
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cpf.org.sa can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cpf.org.sa main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
cpf.org.sa
Open Graph description is not detected on the main page of Cpf. 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: