Tools & Wizards About Us
yzaam.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

yzaam.com

شركة الاهلة للسياحة

Page Load Speed

5.5 sec in total

First Response

238 ms

Resources Loaded

4.9 sec

Page Rendered

372 ms

yzaam.com screenshot

About Website

Visit yzaam.com now to see the best up-to-date Yzaam content for Saudi Arabia and also check out these interesting facts you probably never knew about yzaam.com

شركة الأهلة للسياحة، احجز غرفتك المجاورة للحرم، استفد من خصوماتنا

Visit yzaam.com

Key Findings

We analyzed Yzaam.com page load time and found that the first response time was 238 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

yzaam.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value4,470 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

yzaam.com

238 ms

www.yzaam.com

606 ms

script.js

550 ms

gtm.js

169 ms

bundle.js

399 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Yzaam.com, 50% (13 requests) were made to Le-de.cdn-website.com and 15% (4 requests) were made to Static.cdn-website.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Le-de.cdn-website.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 276.3 kB (22%)

Content Size

1.2 MB

After Optimization

954.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Yzaam.com main page is 1.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. 50% of websites need less resources to load. Images take 774.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 161.3 kB

  • Original 199.2 kB
  • After minification 194.3 kB
  • After compression 37.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 161.3 kB or 81% of the original size.

Image Optimization

-15%

Potential reduce by 114.9 kB

  • Original 774.9 kB
  • After minification 659.9 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, Yzaam needs image optimization as it can save up to 114.9 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 109 B

  • Original 256.4 kB
  • After minification 256.4 kB
  • After compression 256.3 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 7 (33%)

Requests Now

21

After Optimization

14

  • Images
  • JavaScript

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

Network Requests Diagram

yzaam.com

yzaam.com

238 ms

www.yzaam.com

www.yzaam.com

606 ms

script.js

script.js

550 ms

gtm.js

gtm.js

169 ms

bundle.js

bundle.js

399 ms

astqwp4jrC6HR

astqwp4jrC6HR

219 ms

red+white+and+black+colors+business+card+%281%29+%283%29-1920w.png

red+white+and+black+colors+business+card+%281%29+%283%29-1920w.png

651 ms

jquery-3.7.0.min.js

jquery-3.7.0.min.js

83 ms

d-js-one-runtime-unified-desktop.min.js

d-js-one-runtime-unified-desktop.min.js

81 ms

d-js-jquery-migrate.min.js

d-js-jquery-migrate.min.js

78 ms

js

js

118 ms

red+white+and+black+colors+business+card+%281%29+%283%29-146w.png

red+white+and+black+colors+business+card+%281%29+%283%29-146w.png

495 ms

-D8-A8-D9-84-D8-A7--D8-B9-D9-86-D9-88-D8-A7-D9-86-708w.png

-D8-A8-D9-84-D8-A7--D8-B9-D9-86-D9-88-D8-A7-D9-86-708w.png

3883 ms

275943508_1006343379973306_8101865638742368532_n-708w.jpeg

275943508_1006343379973306_8101865638742368532_n-708w.jpeg

1389 ms

Snapinsta.app_346510918_1465912084155024_595279740753609946_n_1080-708w.jpg

Snapinsta.app_346510918_1465912084155024_595279740753609946_n_1080-708w.jpg

2403 ms

300549241_602291731559337_604791703341324041_n-708w.jpeg

300549241_602291731559337_604791703341324041_n-708w.jpeg

2245 ms

312469271_495059495998567_8168668035407050859_n-708w.jpeg

312469271_495059495998567_8168668035407050859_n-708w.jpeg

1832 ms

306916883_869802053986305_7115591910329814093_n-708w.jpeg

306916883_869802053986305_7115591910329814093_n-708w.jpeg

2268 ms

339970550_1199267607404046_6620380653258320372_n-708w.jpeg

339970550_1199267607404046_6620380653258320372_n-708w.jpeg

3464 ms

317610630_665854975134615_8258802665238032264_n-708w.jpeg

317610630_665854975134615_8258802665238032264_n-708w.jpeg

3067 ms

314479020_650893869948918_4788083060975658555_n-708w.jpeg

314479020_650893869948918_4788083060975658555_n-708w.jpeg

4087 ms

333636125_122156924021248_6032918166825261867_n-708w.jpeg

333636125_122156924021248_6032918166825261867_n-708w.jpeg

4011 ms

red+white+and+black+colors+business+card+%281%29+%283%29-130w.png

red+white+and+black+colors+business+card+%281%29+%283%29-130w.png

2848 ms

Dubai-Bold-1b76_400.ttf

Dubai-Bold-1b76_400.ttf

947 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

4 ms

Dubai-Regular-10df_400.ttf

Dubai-Regular-10df_400.ttf

38 ms

Accessibility Review

yzaam.com accessibility score

79

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

yzaam.com 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

SEO Factors

yzaam.com SEO score

86

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 Yzaam.com 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 Yzaam.com 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

yzaam.com

Open Graph data is detected on the main page of Yzaam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: