4.6 sec in total
1.3 sec
3 sec
385 ms
Welcome to shaya.com.sa homepage info - get ready to check Shaya best content for Saudi Arabia right away, or after learning these important things about shaya.com.sa
Visit shaya.com.saWe analyzed Shaya.com.sa page load time and found that the first response time was 1.3 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
shaya.com.sa performance score
name
value
score
weighting
Value20.1 s
0/100
10%
Value59.2 s
0/100
25%
Value72.6 s
0/100
10%
Value350 ms
73/100
30%
Value0.301
39/100
15%
Value75.3 s
0/100
10%
1264 ms
221 ms
27 ms
116 ms
64 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 67% of them (96 requests) were addressed to the original Shaya.com.sa, 17% (25 requests) were made to Maps.google.com and 5% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Shaya.com.sa.
Page size can be reduced by 4.4 MB (23%)
19.4 MB
15.0 MB
In fact, the total size of Shaya.com.sa main page is 19.4 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 15.9 MB which makes up the majority of the site volume.
Potential reduce by 125.4 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 125.4 kB or 85% of the original size.
Potential reduce by 1.6 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. Shaya images are well optimized though.
Potential reduce by 929.8 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 929.8 kB or 67% of the original size.
Potential reduce by 1.8 MB
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. Shaya.com.sa needs all CSS files to be minified and compressed as it can save up to 1.8 MB or 90% of the original size.
Number of requests can be reduced by 65 (48%)
135
70
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shaya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
shaya.com.sa
1264 ms
f=flat-jooza
221 ms
font-awesome.min.css
27 ms
dashicons.min.css
116 ms
jquery-ui-dialog.min.css
64 ms
settings.css
91 ms
css
27 ms
css
37 ms
css
36 ms
settings.css
89 ms
css
36 ms
fontello.css
87 ms
style.css
94 ms
core.animation.css
138 ms
shortcodes.css
163 ms
tribe-style.css
115 ms
skin.css
195 ms
custom-style.css
120 ms
responsive.css
138 ms
skin.responsive.css
141 ms
mediaelementplayer.min.css
149 ms
wp-mediaelement.css
163 ms
js_composer.min.css
277 ms
jquery.js
193 ms
jquery-migrate.min.js
174 ms
lightbox.js
188 ms
jquery.themepunch.tools.min.js
273 ms
jquery.themepunch.essential.min.js
200 ms
jquery.themepunch.revolution.min.js
274 ms
modernizr.min.js
274 ms
core.messages.css
235 ms
core.min.js
236 ms
widget.min.js
235 ms
mouse.min.js
283 ms
resizable.min.js
283 ms
draggable.min.js
284 ms
button.min.js
284 ms
position.min.js
283 ms
dialog.min.js
284 ms
wpdialog.min.js
284 ms
superfish.min.js
285 ms
core.utils.js
285 ms
js
21 ms
core.init.js
300 ms
mediaelement-and-player.min.js
285 ms
wp-mediaelement.js
260 ms
social-share.js
259 ms
comment-reply.min.js
259 ms
core.debug.js
252 ms
wp-embed.min.js
236 ms
shortcodes.js
239 ms
core.messages.js
234 ms
js_composer_front.min.js
218 ms
isotope.pkgd.min.js
217 ms
core.googlemap.js
214 ms
wp-emoji-release.min.js
131 ms
logo-1.png
66 ms
Festina-Ladies-1920x890-dot-sa.jpg
67 ms
Nixon-1920x890-dot-sa.jpg
108 ms
DW-1920x890-dot-sa.jpg
109 ms
Raymond-Weil-1920x890-dot-sa.jpg
111 ms
Esprit-1920x890-dot-sa.jpg
107 ms
Storm-1920x890-dot-sa.jpg
181 ms
CAT-1920x890-pix.jpg
177 ms
Avalieri-1920x890-dot-sa.jpg
177 ms
RH-1920x890-pix.jpg
179 ms
Bering-1920x890-dot-sa.jpg
181 ms
HL-1920x890-pix.jpg
187 ms
Christian-Bernard-1920x890-dot-sa.jpg
183 ms
Escape-1920x890-dot-sa.jpg
184 ms
Louise-Erard-1920x890-dot-sa.jpg
185 ms
Reebok-1920x890-dot-sa.jpg
259 ms
Seven-Friday-1920x890-dot-sa.jpg
256 ms
Frederique-Constant-1920x890-dot-sa.jpg
258 ms
Avalieri-Ladies-1920x890-dot-sa.jpg
259 ms
2.jpg
260 ms
05-Avalieri-Logo-Time.jpg
261 ms
fes-1.jpg
261 ms
rqmnh_logo.png
262 ms
flat-jooza-regular.woff
384 ms
fontello.woff
65 ms
fontawesome-webfont.woff
63 ms
revolution.extension.slideanims.min.js
101 ms
revolution.extension.navigation.min.js
104 ms
revolution.extension.parallax.min.js
102 ms
common.js
55 ms
map.js
56 ms
util.js
55 ms
geocoder.js
56 ms
marker.js
55 ms
Festina-Ladies-1920x890-dot-sa-100x50.jpg
41 ms
Nixon-1920x890-dot-sa-100x50.jpg
69 ms
DW-1920x890-dot-sa-100x50.jpg
68 ms
Raymond-Weil-1920x890-dot-sa-100x50.jpg
70 ms
Esprit-1920x890-dot-sa-100x50.jpg
70 ms
Storm-1920x890-dot-sa-100x50.jpg
69 ms
CAT-1920x890-pix-100x50.jpg
69 ms
Avalieri-1920x890-dot-sa-100x50.jpg
76 ms
RH-1920x890-pix-100x50.jpg
75 ms
Bering-1920x890-dot-sa-100x50.jpg
77 ms
HL-1920x890-pix-100x50.jpg
76 ms
Christian-Bernard-1920x890-dot-sa-100x50.jpg
78 ms
Escape-1920x890-dot-sa-100x50.jpg
77 ms
Louise-Erard-1920x890-dot-sa-100x50.jpg
104 ms
Reebok-1920x890-dot-sa-100x50.jpg
103 ms
Seven-Friday-1920x890-dot-sa-100x50.jpg
105 ms
Frederique-Constant-1920x890-dot-sa-100x50.jpg
105 ms
Avalieri-Ladies-1920x890-dot-sa-100x50.jpg
106 ms
onion.js
40 ms
openhand_8_8.cur
29 ms
AuthenticationService.Authenticate
168 ms
GeocodeService.Search
641 ms
revicons.woff
109 ms
ViewportInfoService.GetViewportInfo
217 ms
controls.js
10 ms
transparent.png
77 ms
css
98 ms
48.gif
119 ms
google_white5.png
50 ms
mapcnt6.png
96 ms
sv9.png
96 ms
tmapctrl.png
66 ms
tmapctrl4.png
66 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
62 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
63 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
63 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
63 ms
vt
115 ms
vt
73 ms
vt
71 ms
vt
72 ms
vt
72 ms
vt
70 ms
vt
111 ms
vt
75 ms
vt
74 ms
vt
78 ms
vt
107 ms
vt
89 ms
vt
91 ms
vt
94 ms
vt
116 ms
vt
127 ms
vt
88 ms
shaya.com.sa 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
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.
shaya.com.sa 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
shaya.com.sa SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
AR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shaya.com.sa can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and it does not match the claimed English language. Our system also found out that Shaya.com.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.
shaya.com.sa
Open Graph description is not detected on the main page of Shaya. 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: