3.3 sec in total
265 ms
2.8 sec
228 ms
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.comWe analyzed Yzaam.com page load time and found that the first response time was 265 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.
yzaam.com performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value9.4 s
1/100
25%
Value5.6 s
53/100
10%
Value290 ms
79/100
30%
Value0.426
22/100
15%
Value9.1 s
33/100
10%
265 ms
462 ms
93 ms
144 ms
144 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that all of those requests were addressed to Yzaam.com and no external sources were called. The less responsive or slowest element that took the longest time to load (825 ms) belongs to the original domain Yzaam.com.
Page size can be reduced by 433.8 kB (39%)
1.1 MB
685.7 kB
In fact, the total size of Yzaam.com main page is 1.1 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. 35% of websites need less resources to load. Images take 626.2 kB which makes up the majority of the site volume.
Potential reduce by 20.7 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 20.7 kB or 83% of the original size.
Potential reduce by 73.6 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 73.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 287.7 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 287.7 kB or 71% of the original size.
Potential reduce by 51.9 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. Yzaam.com needs all CSS files to be minified and compressed as it can save up to 51.9 kB or 81% of the original size.
Number of requests can be reduced by 31 (62%)
50
19
The browser has sent 50 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 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
yzaam.com
265 ms
462 ms
pjWebRTL.css
93 ms
owl.carousel.css
144 ms
owl.theme.css
144 ms
jquery-ui.min.css
161 ms
pjWebHomeRTL.css
165 ms
pjWebFormsRTL.css
136 ms
jquery-1.11.0.min.js
301 ms
pjWeb.js
255 ms
owl.carousel.min.js
267 ms
jquery-ui.custom.min.js
581 ms
jquery.validate.min.js
265 ms
pjWebHome.js
334 ms
pjWebSuggest.js
393 ms
pjWebSearch.js
404 ms
pjWebForms.js
354 ms
reset.css
283 ms
header.png
112 ms
t_c4ca4238a0b923820dcc509a6f75849b.png
106 ms
dest-down.png
110 ms
ar.png
102 ms
us.png
94 ms
nav-limiter.png
85 ms
main-home.png
184 ms
carousel-prev.png
174 ms
t_e4da3b7fbbce2345d7772b0674a318d5.jpg
371 ms
t_1679091c5a880faf6fb5e6087eb1b2dc.jpg
369 ms
t_8f14e45fceea167a5a36dedd4bea2543.jpg
363 ms
carousel-next.png
192 ms
filter-down.png
307 ms
clear.png
257 ms
owl-carousel-prev.png
330 ms
65_2909baa4cd56d53bf8e0d089ecb1f7b0.jpg
332 ms
17_33a8dbd4dc29b557d8d28683978abd65.jpg
469 ms
14_e72707f79cf8738d5e2d8e5d1462803c.png
497 ms
13_9dcd22270917234f8fbdee014e345571.jpg
438 ms
12_31283af71c86798db84f6bf4ac23e10e.jpg
483 ms
owl-carousel-next.png
494 ms
9_5a4a65f40ee3d4c2b4ef51d2ecfb48a5.png
675 ms
8fe403a282f74bc72fa0cc1b90f66b65.jpg
688 ms
social-facebook.png
546 ms
social-twitter.png
603 ms
edbef02e7b20cc9bec69186f2be8d486.png
603 ms
99ffed83e72a0382001a91f4656b035b.png
586 ms
footer.png
714 ms
stars.png
749 ms
season.png
680 ms
nights.png
806 ms
pin.png
817 ms
badge-discount.png
822 ms
ajax-load.gif
825 ms
yzaam.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
yzaam.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
yzaam.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
AR
AR
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.
yzaam.com
Open Graph description is not detected on the main page of Yzaam. 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: