Report Summary

  • 67

    Performance

    Renders faster than
    80% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

smt.sa

SMT

Page Load Speed

3.3 sec in total

First Response

848 ms

Resources Loaded

1.8 sec

Page Rendered

621 ms

smt.sa screenshot

About Website

Click here to check amazing SMT content for Saudi Arabia. Otherwise, check out these important facts you probably never knew about smt.sa

SMT

Visit smt.sa

Key Findings

We analyzed Smt.sa page load time and found that the first response time was 848 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

smt.sa performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

48/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

smt.sa

848 ms

bootstrap.min.css

106 ms

font-awesome.min.css

94 ms

owl.carousel.css

65 ms

animate.css

88 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 54% of them (44 requests) were addressed to the original Smt.sa, 21% (17 requests) were made to Google.com and 13% (11 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (848 ms) belongs to the original domain Smt.sa.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (32%)

Content Size

3.2 MB

After Optimization

2.2 MB

In fact, the total size of Smt.sa main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 29.6 kB

  • Original 35.5 kB
  • After minification 26.6 kB
  • After compression 5.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 8.9 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 29.6 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 133.0 kB

  • Original 2.0 MB
  • After minification 1.9 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. SMT images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 652.4 kB

  • Original 925.4 kB
  • After minification 902.8 kB
  • After compression 273.0 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 652.4 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 206.5 kB

  • Original 239.3 kB
  • After minification 217.5 kB
  • After compression 32.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. Smt.sa needs all CSS files to be minified and compressed as it can save up to 206.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (30%)

Requests Now

81

After Optimization

57

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

Accessibility Review

smt.sa accessibility score

89

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

smt.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

Page has valid source maps

SEO Factors

smt.sa SEO score

92

Search Engine Optimization Advices

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 Smt.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 Smt.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

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