7.7 sec in total
1.1 sec
5.6 sec
1 sec
Welcome to shareyah.com homepage info - get ready to check Shareyah best content right away, or after learning these important things about shareyah.com
Visit shareyah.comWe analyzed Shareyah.com page load time and found that the first response time was 1.1 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
shareyah.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value11.9 s
0/100
25%
Value11.3 s
5/100
10%
Value1,030 ms
26/100
30%
Value0.141
78/100
15%
Value10.7 s
22/100
10%
1104 ms
193 ms
192 ms
281 ms
40 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 87% of them (68 requests) were addressed to the original Shareyah.com, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Shareyah.com.
Page size can be reduced by 1.2 MB (22%)
5.4 MB
4.2 MB
In fact, the total size of Shareyah.com main page is 5.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. 55% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 73.1 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 73.1 kB or 84% of the original size.
Potential reduce by 182.3 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. Shareyah images are well optimized though.
Potential reduce by 539.4 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 539.4 kB or 67% of the original size.
Potential reduce by 399.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. Shareyah.com needs all CSS files to be minified and compressed as it can save up to 399.8 kB or 86% of the original size.
Number of requests can be reduced by 29 (41%)
70
41
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shareyah. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
shareyah.com
1104 ms
styles.css
193 ms
styles-rtl.css
192 ms
layerslider.css
281 ms
css
40 ms
settings.css
402 ms
js_composer.css
475 ms
font-awesome.min.css
463 ms
style.css
750 ms
visual-composer-custom.css
559 ms
visual-composer-extend.css
684 ms
responsive.css
688 ms
skin.css
657 ms
gmw.css
658 ms
jquery.js
1035 ms
jquery-migrate.min.js
842 ms
layerslider.kreaturamedia.jquery.js
1069 ms
greensock.js
1084 ms
layerslider.transitions.js
954 ms
jquery.themepunch.tools.min.js
1207 ms
jquery.themepunch.revolution.min.js
1311 ms
rtl.css
1206 ms
css
69 ms
jquery.form.min.js
955 ms
scripts.js
955 ms
total-min.js
1483 ms
jquery.colorbox.min.js
1077 ms
gmw.js
1102 ms
js_composer_front.js
1206 ms
analytics.js
8 ms
collect
43 ms
collect
76 ms
%D9%87%D9%8A%D8%AF%D8%B1.png
217 ms
staticmap
73 ms
%D8%A8%D8%A7%D8%AA%D8%B1%D9%86-2.png
263 ms
blank.gif
209 ms
%D8%AD%D8%AC-%D9%88%D8%B9%D9%85%D8%B1%D8%A92-90x90.jpg
206 ms
%D9%85%D8%B7%D8%A8%D8%AE-%D8%A7%D9%84%D8%AC%D9%85%D8%B9%D9%8A%D8%A9-90x90.jpg
249 ms
%D9%84%D9%88%D8%AC%D9%88-%D8%B4%D8%BA%D9%84-%D8%A7%D9%8A%D8%AF%D9%8A%D9%86%D8%A71-90x90.jpg
359 ms
%D9%83%D8%AA%D8%A7%D8%AA%D9%8A%D8%A8-%D8%A7%D9%84%D8%AA%D8%AD%D9%81%D9%8A%D8%B81-90x90.jpg
391 ms
%D8%AF%D8%A7%D8%B1-%D8%A7%D9%84%D8%B3%D9%8A%D8%AF%D8%A9-%D8%AE%D8%AF%D9%8A%D8%AC%D8%A9-90x90.jpg
389 ms
%D8%AA%D8%B4%D8%BA%D9%8A%D9%84-%D8%A7%D9%85%D9%87%D8%A7%D8%AA-%D8%A7%D9%84%D8%A7%D9%8A%D8%AA%D8%A7%D9%85-90x90.jpg
432 ms
%D8%AD%D9%81%D8%B8-%D8%A7%D9%84%D9%82%D8%B1%D8%A7%D9%861.png
831 ms
%D9%83%D9%81%D8%A7%D9%84%D8%A9-%D8%A7%D9%84%D9%8A%D8%AA%D9%8A%D9%85.png
832 ms
109.jpg
935 ms
%D8%A7%D9%84%D9%85%D9%83%D8%AA%D8%A8%D8%A9.png
833 ms
%D8%AD%D8%B6%D8%A7%D9%86%D8%A7%D8%AA.png
834 ms
%D8%BA%D8%B3%D9%8A%D9%84-%D8%A7%D9%84%D9%83%D9%84%D9%89.png
839 ms
%D8%A7%D9%84%D9%85%D8%B4%D8%B1%D9%88%D8%B9%D8%A7%D8%AA-%D8%A7%D9%84%D8%A5%D8%AC%D8%AA%D9%85%D8%A7%D8%B9%D9%8A%D8%A9-.jpg
1411 ms
%D8%A7%D9%84%D9%85%D8%B4%D8%B1%D9%88%D8%B9%D8%A7%D8%AA-%D8%A7%D9%84%D8%B7%D8%A8%D9%8A%D8%A9.jpg
1190 ms
%D9%83%D8%A7%D9%85%D9%8A%D8%B1%D8%A7-%D8%A7%D9%84%D8%AC%D9%85%D8%B9%D9%8A%D8%A91.jpg
1306 ms
%D9%85%D8%B4%D8%B1%D9%88%D8%B9%D8%A7%D8%AA-%D8%A7%D9%84%D8%AA%D8%B9%D9%84%D9%8A%D9%85.jpg
1758 ms
%D9%85%D9%86-%D8%A7%D9%86%D8%B4%D8%B7%D8%A9-%D8%A7%D9%84%D8%AC%D9%85%D8%B9%D9%8A%D8%A9-.jpg
1452 ms
dot.png
1094 ms
DroidNaskh-Regular.woff
25 ms
DroidNaskh-Bold.woff
27 ms
fontawesome-webfont.woff
1468 ms
%D9%87%D9%8A%D8%AF%D8%B1.png
1564 ms
skin.css
907 ms
skin.css
1149 ms
1901332_10203959151796305_4212243664197117444_n.jpg
187 ms
blank.gif
100 ms
ls-arrow-left.png
186 ms
ls-arrow-right.png
187 ms
3.png
500 ms
skin.png
193 ms
%D8%AE%D8%A8%D8%B1-%D9%85%D8%B9%D8%B1%D8%B6-%D8%A7%D9%84%D9%83%D8%AA%D8%A7%D8%A8-2.jpg
846 ms
%D8%B9%D9%85%D8%B1%D8%A9-2.jpg
932 ms
44444444444444444444444444444444444444444444444444444444444444.jpg
1045 ms
123%D9%88%D9%82%D9%81-%D8%A7%D9%84%D9%8A%D8%AA%D9%8A%D9%85.jpg
768 ms
12176298_10153729863524588_764671614_o.jpg
584 ms
%D8%AA%D9%86%D8%A8%D9%8A%D9%87-%D9%84%D9%84%D8%B5%D9%81%D8%AD%D8%A7%D8%AA.jpg
1070 ms
%D9%88%D9%82%D9%81-%D8%A7%D9%84%D9%8A%D8%AA%D9%8A%D9%85.jpg
1230 ms
skin.png
954 ms
1901332_10203959151796305_4212243664197117444_n.jpg
1058 ms
loading.gif
815 ms
loading.gif
741 ms
2.png
1146 ms
shareyah.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
shareyah.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
shareyah.com SEO score
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
Tap targets are not sized appropriately
AR
AR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shareyah.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 Shareyah.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.
shareyah.com
Open Graph description is not detected on the main page of Shareyah. 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: