Tools & Wizards About Us
vision2030.gov.sa screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

vision2030.gov.sa

رؤية السعودية 2030

Page Load Speed

3.3 sec in total

First Response

197 ms

Resources Loaded

2.2 sec

Page Rendered

835 ms

vision2030.gov.sa screenshot

About Website

Click here to check amazing Vision 2030 content for Saudi Arabia. Otherwise, check out these important facts you probably never knew about vision2030.gov.sa

Visit vision2030.gov.sa

Key Findings

We analyzed Vision2030.gov.sa page load time and found that the first response time was 197 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

vision2030.gov.sa performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value82.4 s

0/100

25%

SI (Speed Index)

Value96.9 s

0/100

10%

TBT (Total Blocking Time)

Value3,360 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value85.2 s

0/100

10%

Network Requests Diagram

vision2030.gov.sa

197 ms

www.vision2030.gov.sa

256 ms

gtm.js

98 ms

3136bf1aa4975a47.css

130 ms

2c91dbfd81417c54.css

430 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 98% of them (96 requests) were addressed to the original Vision2030.gov.sa, 1% (1 request) were made to Googletagmanager.com and 1% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Vision2030.gov.sa.

Page Optimization Overview & Recommendations

Page size can be reduced by 984.3 kB (3%)

Content Size

28.5 MB

After Optimization

27.5 MB

  • HTML
  • Images

In fact, the total size of Vision2030.gov.sa main page is 28.5 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. Only a small number of websites need less resources to load. Images take 27.9 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 590.0 kB

  • Original 655.6 kB
  • After minification 639.3 kB
  • After compression 65.6 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 590.0 kB or 90% of the original size.

Image Optimization

-1%

Potential reduce by 394.3 kB

  • Original 27.9 MB
  • After minification 27.5 MB

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. Vision 2030 images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 23 (26%)

Requests Now

90

After Optimization

67

  • Images
  • JavaScript
  • CSS

The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vision 2030. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vision2030.gov.sa

vision2030.gov.sa

197 ms

www.vision2030.gov.sa

www.vision2030.gov.sa

256 ms

gtm.js

gtm.js

98 ms

3136bf1aa4975a47.css

3136bf1aa4975a47.css

130 ms

2c91dbfd81417c54.css

2c91dbfd81417c54.css

430 ms

507344e816f4d9ea.css

507344e816f4d9ea.css

160 ms

28813663729aaa5e.css

28813663729aaa5e.css

194 ms

9bc10296b0788ec2.css

9bc10296b0788ec2.css

167 ms

41ad6169c350fe8f.css

41ad6169c350fe8f.css

136 ms

e01d37e49258dbc8.css

e01d37e49258dbc8.css

147 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

257 ms

688.fb01690e5c7fad35.js

688.fb01690e5c7fad35.js

162 ms

497.e14024794bb85659.js

497.e14024794bb85659.js

195 ms

webpack-a84098d7c9350893.js

webpack-a84098d7c9350893.js

195 ms

framework-885bb1bdaf7625f7.js

framework-885bb1bdaf7625f7.js

196 ms

main-5ede3010de4b227b.js

main-5ede3010de4b227b.js

206 ms

_app-33b751f73f6136f8.js

_app-33b751f73f6136f8.js

291 ms

94726e6d-7101548bee60cb4f.js

94726e6d-7101548bee60cb4f.js

621 ms

725-f7bd71424971b759.js

725-f7bd71424971b759.js

293 ms

457-336ab2231d5ed9d3.js

457-336ab2231d5ed9d3.js

236 ms

694-4c8679955f9711e5.js

694-4c8679955f9711e5.js

366 ms

211-5bff25fecb69e85c.js

211-5bff25fecb69e85c.js

654 ms

979-bae37c23c568983d.js

979-bae37c23c568983d.js

320 ms

index-8576a31ef273af7a.js

index-8576a31ef273af7a.js

310 ms

_buildManifest.js

_buildManifest.js

323 ms

_ssgManifest.js

_ssgManifest.js

598 ms

image

image

329 ms

Main-2_00061.webp

Main-2_00061.webp

350 ms

image

image

369 ms

image

image

885 ms

image

image

598 ms

image

image

588 ms

image

image

590 ms

image

image

591 ms

image

image

591 ms

image

image

594 ms

image

image

593 ms

image

image

595 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

86 ms

image

image

573 ms

image

image

482 ms

image

image

480 ms

image

image

473 ms

image

image

457 ms

image

image

476 ms

image

image

427 ms

image

image

427 ms

image

image

443 ms

image

image

1316 ms

image

image

442 ms

image

image

434 ms

image

image

1280 ms

image

image

357 ms

image

image

356 ms

image

image

353 ms

image

image

338 ms

image

image

330 ms

image

image

329 ms

image

image

323 ms

image

image

306 ms

image

image

304 ms

image

image

293 ms

image

image

83 ms

image

image

76 ms

image

image

85 ms

image

image

85 ms

image

image

104 ms

image

image

104 ms

image

image

99 ms

image

image

120 ms

image

image

117 ms

image

image

113 ms

image

image

128 ms

image

image

135 ms

image

image

131 ms

image

image

137 ms

image

image

142 ms

image

image

148 ms

image

image

136 ms

image

image

140 ms

image

image

153 ms

image

image

147 ms

image

image

151 ms

image

image

159 ms

29LTBukra-Regular.3dc043a0.woff

29LTBukra-Regular.3dc043a0.woff

867 ms

29LTBukra.ae2d6d28.woff

29LTBukra.ae2d6d28.woff

663 ms

29LTBukra-Medium.47cea708.woff

29LTBukra-Medium.47cea708.woff

850 ms

29LTBukra-Light.6aed01de.woff

29LTBukra-Light.6aed01de.woff

367 ms

29LTBukra-Bold.cf7cae79.woff

29LTBukra-Bold.cf7cae79.woff

509 ms

29LTBukra-Black.591c9ddf.woff

29LTBukra-Black.591c9ddf.woff

1025 ms

image

image

701 ms

image

image

701 ms

image

image

699 ms

image

image

829 ms

image

image

829 ms

image

image

827 ms

tick.84cd9224.png

tick.84cd9224.png

826 ms

pattern-bg.97a3ab15.png

pattern-bg.97a3ab15.png

822 ms

Accessibility Review

vision2030.gov.sa accessibility score

71

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

vision2030.gov.sa best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

vision2030.gov.sa SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    AR

  • Language Claimed

    AR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vision2030.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 Vision2030.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.

Social Sharing Optimization

vision2030.gov.sa

Open Graph description is not detected on the main page of Vision 2030. 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: