7.8 sec in total
504 ms
7 sec
281 ms
Welcome to yesser.gov.sa homepage info - get ready to check Yesser best content for Saudi Arabia right away, or after learning these important things about yesser.gov.sa
برنامج التعاملات الإلكترونية الحكومية (يسّر) حكومة رقمية فاعلة تضع المواطن أولاً
Visit yesser.gov.saWe analyzed Yesser.gov.sa page load time and found that the first response time was 504 ms 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.
yesser.gov.sa performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value12.1 s
0/100
25%
Value12.8 s
2/100
10%
Value240 ms
85/100
30%
Value0.041
99/100
15%
Value12.7 s
14/100
10%
504 ms
2591 ms
488 ms
788 ms
484 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 96% of them (82 requests) were addressed to the original Yesser.gov.sa, 1% (1 request) were made to Code.jquery.com and 1% (1 request) were made to Static.getclicky.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Yesser.gov.sa.
Page size can be reduced by 2.0 MB (73%)
2.8 MB
746.5 kB
In fact, the total size of Yesser.gov.sa main page is 2.8 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. 70% of websites need less resources to load. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 78.4 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 78.4 kB or 77% of the original size.
Potential reduce by 42.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. Yesser images are well optimized though.
Potential reduce by 1.6 MB
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 1.6 MB or 85% of the original size.
Potential reduce by 343.5 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. Yesser.gov.sa needs all CSS files to be minified and compressed as it can save up to 343.5 kB or 87% of the original size.
Number of requests can be reduced by 52 (65%)
80
28
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yesser. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
yesser.gov.sa
504 ms
default.aspx
2591 ms
controls.css
488 ms
corev4.css
788 ms
layouts.css
484 ms
minimalv4.css
492 ms
page-layouts-21.css
368 ms
search.css
711 ms
styleAr.css
812 ms
scriptsAr.js
672 ms
DetectMobileBrowserAR.js
673 ms
jquery-latest.min.js
6 ms
jquery.colorbox-min.js
694 ms
colorbox.css
853 ms
WebResource.axd
511 ms
ScriptResource.axd
537 ms
blank.debug.js
547 ms
nivo-slider.css
617 ms
jquery.nivo.slider.js
646 ms
slick.css
677 ms
slick-theme.css
675 ms
slick.min.js
711 ms
jQueryScrollTo.js
725 ms
jQueryCycle.js
782 ms
smoothDivScroll_ar.css
826 ms
jquery.ui.widget.js
851 ms
jquery.smoothDivScroll-1.0.js
850 ms
js
7 ms
init.debug.js
621 ms
ScriptResource.axd
818 ms
ScriptResource.axd
668 ms
srchbtn-bg.png
215 ms
logo.gif
223 ms
b1.jpg
490 ms
b2.jpg
378 ms
b3.jpg
361 ms
B4.jpg
348 ms
sliber-bottom.jpg
400 ms
3.png
410 ms
1.png
532 ms
2.png
533 ms
4.png
554 ms
5.png
587 ms
88.png
591 ms
87.png
673 ms
86.png
698 ms
85.png
701 ms
84.png
731 ms
loading.gif
770 ms
homeHeadBg.png
781 ms
loginBtnHome.png
833 ms
login-btn.png
852 ms
searchCurve.png
857 ms
searchBtn.png
888 ms
bgximg.png
935 ms
headerShadowBg.png
952 ms
yesser_menu_bg.png
993 ms
homeBottomBG.png
1003 ms
aboutYasserbox.png
1031 ms
homeboxes-more-bg.png
1087 ms
NewsEventsBox.png
1100 ms
homeevents-item-bg.png
1151 ms
calendarBG.png
1149 ms
releasesBox.png
1163 ms
footerBg.png
1186 ms
facebook.png
1253 ms
in.php
137 ms
youtube.png
1167 ms
twitter.png
1038 ms
linkedin.png
1030 ms
google.png
1061 ms
rss.png
1119 ms
ajax-loader.gif
1103 ms
carousel-controls-right-bg.png
1098 ms
carousel-controls-left-bg.png
1035 ms
slick.ttf
256 ms
bullets.png
194 ms
core.debug.js
360 ms
sp.core.debug.js
160 ms
ScriptResx.ashx
173 ms
cui.debug.js
494 ms
sp.ui.dialog.debug.js
164 ms
sp.runtime.debug.js
183 ms
search.js
177 ms
sp.debug.js
367 ms
yesser.gov.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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
yesser.gov.sa best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
yesser.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
AR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yesser.gov.sa can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and it does not match the claimed English language. Our system also found out that Yesser.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.
yesser.gov.sa
Open Graph description is not detected on the main page of Yesser. 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: