26.1 sec in total
684 ms
24.4 sec
975 ms
Welcome to sang.gov.sa homepage info - get ready to check Sang best content for Saudi Arabia right away, or after learning these important things about sang.gov.sa
Ministry of National Guard
Visit sang.gov.saWe analyzed Sang.gov.sa page load time and found that the first response time was 684 ms and then it took 25.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
sang.gov.sa performance score
name
value
score
weighting
Value15.0 s
0/100
10%
Value28.1 s
0/100
25%
Value19.9 s
0/100
10%
Value490 ms
59/100
30%
Value0
100/100
15%
Value42.2 s
0/100
10%
684 ms
1053 ms
494 ms
515 ms
990 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 92% of them (92 requests) were addressed to the original Sang.gov.sa, 3% (3 requests) were made to Img.youtube.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Raqmi.dga.gov.sa.
Page size can be reduced by 109.3 kB (59%)
184.6 kB
75.3 kB
In fact, the total size of Sang.gov.sa main page is 184.6 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. 70% of websites need less resources to load. HTML takes 136.4 kB which makes up the majority of the site volume.
Potential reduce by 109.2 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 109.2 kB or 80% of the original size.
Potential reduce by 2 B
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. Sang images are well optimized though.
Potential reduce by 50 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 48 (51%)
94
46
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
sang.gov.sa
684 ms
default.aspx
1053 ms
corev15.css
494 ms
initstrings.js
515 ms
init.js
990 ms
theming.js
519 ms
ScriptResource.axd
669 ms
blank.js
520 ms
ScriptResource.axd
664 ms
jquery-3.6.1.min.js
1955 ms
bootstrap.rtl-5.2.2.min.css
835 ms
all.css
836 ms
meanmenu.css
832 ms
slick.css
837 ms
owl.carousel-2.3.4.min.css
1027 ms
main.css
1028 ms
responsive.css
1028 ms
colorbox.css
1029 ms
video-js.min.css
1160 ms
RacelInternetPortal.css
1170 ms
redmond.calendars.picker.css
1178 ms
modernizr-3.5.0.min.js
1174 ms
jquery.maxlength.css
1173 ms
WebResource.axd
1334 ms
cascade-slider.js
1182 ms
bootstrap.bundle-5.2.2.min.js
1184 ms
meanmenu.js
1185 ms
slick.min.js
1190 ms
owl.carousel-2.3.4.min.js
1349 ms
magnific-popup.min.js
1349 ms
main.js
1353 ms
Home.js
1355 ms
jquery.colorbox-min.js
1361 ms
jwplayer.js
1520 ms
video.js
1518 ms
PrintScript.js
1523 ms
jquery.plugin.js
1525 ms
js
52 ms
jquery.calendars.js
1530 ms
jquery.calendars.plus.js
1338 ms
jquery.calendars.picker.js
1335 ms
jquery.calendars.ummalqura.js
1337 ms
jquery.calendars.ummalqura-ar.js
1342 ms
utils.js
1202 ms
jquery.plugin.min.js
1366 ms
jquery.maxlength.min.js
1203 ms
MaxLength.js
1201 ms
3346
20467 ms
HeaderLogo.png
1809 ms
Desktop%201.jpg
1385 ms
Mobile%201.jpg
1658 ms
Desktop%202.jpg
1355 ms
Mobile%202.jpg
1378 ms
Desktop%203.jpg
1720 ms
Mobile%203.jpg
2381 ms
Asset-40.png
2041 ms
%D8%A7%D9%84%D8%AC%D9%87%D8%A7%D8%AA%20%D8%A7%D9%84%D8%AA%D8%A7%D8%A8%D8%B9%D8%A9-03.PNG
1732 ms
%D8%A7%D9%84%D8%AC%D9%87%D8%A7%D8%AA%20%D8%A7%D9%84%D8%AA%D8%A7%D8%A8%D8%B9%D8%A9-01.PNG
1847 ms
%D8%A7%D9%84%D8%AC%D9%87%D8%A7%D8%AA%20%D8%A7%D9%84%D8%AA%D8%A7%D8%A8%D8%B9%D8%A9-02.PNG
1912 ms
%D8%A7%D9%84%D8%AC%D9%87%D8%A7%D8%AA%20%D8%A7%D9%84%D8%AA%D8%A7%D8%A8%D8%B9%D8%A9-04.PNG
1924 ms
%D8%A7%D9%84%D8%AC%D9%87%D8%A7%D8%AA%20%D8%A7%D9%84%D8%AA%D8%A7%D8%A8%D8%B9%D8%A9-05.PNG
2000 ms
%D8%A7%D9%84%D8%A3%D9%85%D9%8A%D8%B1%20%D8%A7%D9%84%D8%AF%D9%83%D8%AA%D9%88%D8%B1%20%D8%B9%D8%A8%D8%AF%D8%A7%D9%84%D8%B9%D8%B2%D9%8A%D8%B2%20%D8%A8%D9%86%20%D9%85%D8%AD%D9%85%D8%AF%20%D8%A8%D9%86%20%D8%B9%D8%A8%D8%AF%D8%A7%D9%84%D8%B9%D8%B2%D9%8A%D8%B2%20%D8%A8%D9%86%20%D8%B9%D9%8A%D9%91%D8%A7%D9%81.JPG
2047 ms
%D8%AE%D8%A8%D8%B1%205.JPG
2783 ms
%D9%85%D8%B1%D9%83%D8%B2%20%D8%AA%D8%AF%D8%B1%D9%8A%D8%A8%20%D8%A7%D9%84%D8%AD%D8%B1%D8%B3%20%D8%A7%D9%84%D9%88%D8%B7%D9%86%D9%8A.JPG
2615 ms
Asset28.png
2200 ms
Asset-30.png
2225 ms
Asset-31.png
2247 ms
ministry.JPEG
2555 ms
%D8%B1%D9%88%D8%A7%D8%A8%D8%B7%20%D8%AA%D9%87%D9%85%D9%83-01.PNG
2407 ms
%D8%B1%D9%88%D8%A7%D8%A8%D8%B7%20%D8%AA%D9%87%D9%85%D9%83-02.PNG
2426 ms
%D8%B1%D9%88%D8%A7%D8%A8%D8%B7%20%D8%AA%D9%87%D9%85%D9%83-04.PNG
2562 ms
siteIcon.png
2577 ms
searchresultui.png
2596 ms
corev15.css
2723 ms
Asset-45.png
7071 ms
sira_bg.png
2734 ms
fa-brands-400.ttf
2853 ms
strings.js
2659 ms
sp.init.js
2773 ms
PortalHandler.ashx
2810 ms
PortalHandler.ashx
2832 ms
PortalHandler.ashx
2848 ms
js
46 ms
analytics.js
20 ms
overlay.png
2875 ms
collect
59 ms
PortalHandler.ashx
223 ms
PortalHandler.ashx
196 ms
PortalHandler.ashx
197 ms
PortalHandler.ashx
206 ms
PortalHandler.ashx
290 ms
0.jpg
32 ms
play.png
341 ms
0.jpg
21 ms
0.jpg
19 ms
PHOTO-2021-03-25-11-17-44%20(1).jpg
361 ms
PHOTO-2021-03-25-11-17-44%20(1).jpg
385 ms
PHOTO-2021-03-25-11-17-44%20(1).jpg
384 ms
fa-solid-900.ttf
921 ms
fa-regular-400.ttf
508 ms
sang.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
Image elements do not have [alt] attributes
Links do not have a discernible 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
sang.gov.sa best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
sang.gov.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
AR
AR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sang.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 Sang.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.
sang.gov.sa
Open Graph description is not detected on the main page of Sang. 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: