3.3 sec in total
365 ms
2.5 sec
483 ms
Visit shaer.us now to see the best up-to-date Shaer content for Egypt and also check out these interesting facts you probably never knew about shaer.us
Building state-of-the-art, easy to use, user-friendly websites and applications is truly a passion of mine.
Visit shaer.usWe analyzed Shaer.us page load time and found that the first response time was 365 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
shaer.us performance score
name
value
score
weighting
Value1.6 s
95/100
10%
Value5.7 s
16/100
25%
Value3.7 s
86/100
10%
Value40 ms
100/100
30%
Value0.001
100/100
15%
Value3.8 s
90/100
10%
365 ms
173 ms
161 ms
164 ms
36 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 74% of them (76 requests) were addressed to the original Shaer.us, 16% (16 requests) were made to Fonts.gstatic.com and 6% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Shaer.us.
Page size can be reduced by 1.0 MB (59%)
1.7 MB
707.4 kB
In fact, the total size of Shaer.us main page is 1.7 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. Javascripts take 889.8 kB which makes up the majority of the site volume.
Potential reduce by 52.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. This page needs HTML code to be minified as it can gain 20.6 kB, which is 34% 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 52.4 kB or 86% of the original size.
Potential reduce by 26.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. Shaer images are well optimized though.
Potential reduce by 650.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 650.3 kB or 73% of the original size.
Potential reduce by 306.6 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. Shaer.us needs all CSS files to be minified and compressed as it can save up to 306.6 kB or 85% of the original size.
Number of requests can be reduced by 63 (74%)
85
22
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shaer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
shaer.us
365 ms
wp-emoji-release.min.js
173 ms
styles.css
161 ms
settings.css
164 ms
css
36 ms
css
40 ms
css
36 ms
settings.css
171 ms
style.css
175 ms
bootstrap.min.css
21 ms
font-awesome.min.css
17 ms
prettify.min.css
173 ms
superslides.min.css
323 ms
animate.min.css
317 ms
owl.carousel.min.css
321 ms
owl.theme.min.css
326 ms
owl.transitions.min.css
329 ms
magnific-popup.min.css
330 ms
superfish.min.css
480 ms
megafolio-style.min.css
484 ms
megafolio-settings.css
477 ms
style.css
487 ms
style-responsive.css
491 ms
apps-reset.min.css
492 ms
widget.min.css
636 ms
css
29 ms
css
28 ms
css
31 ms
jquery.js
640 ms
jquery-migrate.min.js
658 ms
lightbox.js
683 ms
jquery.themepunch.tools.min.js
661 ms
jquery.themepunch.essential.min.js
659 ms
jquery.themepunch.revolution.min.js
797 ms
wow.min.js
795 ms
js
41 ms
jquery.form.min.js
893 ms
scripts.js
894 ms
jquery.wait.min.js
892 ms
jquery.scrollUp.min.js
894 ms
jquery.easing.min.js
970 ms
bootstrap.min.js
19 ms
jquery.superslides.min.js
970 ms
jquery.easypiechart.min.js
971 ms
jquery.nav.min.js
971 ms
jquery.scrollTo.min.js
972 ms
owl.carousel.min.js
939 ms
waypoints.min.js
934 ms
waypoints-sticky.min.js
959 ms
jquery.fittext.min.js
963 ms
jquery.appear.min.js
967 ms
jquery.isotope.min.js
967 ms
jquery.smooth-scroll.min.js
1022 ms
jquery.megafolio.plugins.min.js
934 ms
jquery.themepunch.megafoliopro.min.js
966 ms
jquery.magnific-popup.min.js
967 ms
prettify.min.js
968 ms
jquery-ui-1.10.4.custom.min.js
976 ms
hoverIntent.min.js
976 ms
superfish.min.js
931 ms
jflickrfeed.min.js
979 ms
jquery.nicescroll.js
980 ms
scripts.js
965 ms
navigation.min.js
957 ms
skip-link-focus-fix.min.js
958 ms
comment-reply.min.js
925 ms
background.jpg
927 ms
logo.png
926 ms
shaer.png
927 ms
skills.jpg
928 ms
timeline-divider.jpg
704 ms
grain.png
928 ms
lupe.png
870 ms
email.png
874 ms
github.png
876 ms
linkedin.png
873 ms
instagram.png
885 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
19 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
20 ms
PKCRbVvRfd5n7BTjtGiFZC3USBnSvpkopQaUR-2r7iU.ttf
19 ms
1ImRNPx4870-D9a1EBUdPC3USBnSvpkopQaUR-2r7iU.ttf
18 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
18 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
18 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
42 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
43 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
41 ms
8KhZd3VQBtXTAznvKjw-ky3USBnSvpkopQaUR-2r7iU.ttf
43 ms
RJMlAoFXXQEzZoMSUteGWKCWcynf_cDxXwCLxiixG1c.ttf
45 ms
fontawesome-webfont.woff
5 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
41 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
43 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
42 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
43 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
43 ms
twitter.png
918 ms
sticky-logo.png
906 ms
shaer.us
220 ms
elnahrda-577x500.jpg
188 ms
aldawlia-577x500.jpg
186 ms
pelican-577x500.jpg
195 ms
egyptmineaction-577x500.jpg
276 ms
aop-577x500.jpg
307 ms
adawia-577x500.jpg
271 ms
shaer.us 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
Links do not have a discernible name
shaer.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
shaer.us SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shaer.us can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Shaer.us 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.
shaer.us
Open Graph description is not detected on the main page of Shaer. 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: