Tools & Wizards About Us
shineshines.com screenshot

Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

shineshines.com

سن شاين Sunshine

Page Load Speed

17.1 sec in total

First Response

559 ms

Resources Loaded

15.8 sec

Page Rendered

675 ms

shineshines.com screenshot

About Website

Click here to check amazing Shineshines content. Otherwise, check out these important facts you probably never knew about shineshines.com

اكتشف الفخامة مع عطر الشعر أبلوج من ماركة سن شاين

Visit shineshines.com

Key Findings

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

Performance Metrics

shineshines.com performance score

0

Network Requests Diagram

www.nereid.com

559 ms

jquery-2.1.1.min.js

161 ms

fonts.css

106 ms

bootstrap.min.css

189 ms

bootstrap-theme.css

117 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Shineshines.com, 9% (6 requests) were made to Google-analytics.com and 4% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (8.4 sec) relates to the external source Cnzz.mmstat.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 517.3 kB (17%)

Content Size

3.0 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shineshines.com main page is 3.0 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. 40% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 23.4 kB

  • Original 29.0 kB
  • After minification 28.9 kB
  • After compression 5.5 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 23.4 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 10.9 kB

  • Original 2.3 MB
  • After minification 2.3 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. Shineshines images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 211.0 kB

  • Original 342.3 kB
  • After minification 342.1 kB
  • After compression 131.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 211.0 kB or 62% of the original size.

CSS Optimization

-85%

Potential reduce by 271.9 kB

  • Original 318.8 kB
  • After minification 284.6 kB
  • After compression 46.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. Shineshines.com needs all CSS files to be minified and compressed as it can save up to 271.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (63%)

Requests Now

63

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.nereid.com

www.nereid.com

559 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

161 ms

fonts.css

fonts.css

106 ms

bootstrap.min.css

bootstrap.min.css

189 ms

bootstrap-theme.css

bootstrap-theme.css

117 ms

bootstrap.min.js

bootstrap.min.js

118 ms

font-awesome.min.css

font-awesome.min.css

184 ms

stylesheet.css

stylesheet.css

186 ms

swiper.min.css

swiper.min.css

156 ms

stylesheet_s.css

stylesheet_s.css

222 ms

swiper.min.js

swiper.min.js

232 ms

swiper.config.js

swiper.config.js

230 ms

jquery.mCustomScrollbar.js

jquery.mCustomScrollbar.js

236 ms

jquery.mCustomScrollbar.config.js

jquery.mCustomScrollbar.config.js

228 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

229 ms

gotop.js

gotop.js

235 ms

gotop.css

gotop.css

249 ms

sideFollow.js

sideFollow.js

250 ms

magnific-popup.css

magnific-popup.css

253 ms

common.js

common.js

250 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

252 ms

main.js

main.js

250 ms

conversion.js

conversion.js

223 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

437 ms

fbevents.js

fbevents.js

873 ms

logo.png

logo.png

55 ms

mobile-icon-bag.png

mobile-icon-bag.png

56 ms

i7.jpg

i7.jpg

108 ms

i1.jpg

i1.jpg

69 ms

i3.jpg

i3.jpg

136 ms

20160401_1_m.jpg

20160401_1_m.jpg

311 ms

20160401_2_m.jpg

20160401_2_m.jpg

449 ms

1.jpg

1.jpg

114 ms

2.jpg

2.jpg

159 ms

3.jpg

3.jpg

178 ms

4.jpg

4.jpg

192 ms

20160226_m.jpg

20160226_m.jpg

420 ms

20160301_1.jpg

20160301_1.jpg

407 ms

20160401_3.jpg

20160401_3.jpg

460 ms

gtm.js

gtm.js

355 ms

259 ms

search_btn.png

search_btn.png

238 ms

nav_sp.png

nav_sp.png

334 ms

cart.png

cart.png

591 ms

20160401_1.jpg

20160401_1.jpg

650 ms

20160401_2.jpg

20160401_2.jpg

684 ms

20160226.jpg

20160226.jpg

861 ms

social.png

social.png

409 ms

ico-down-b.png

ico-down-b.png

429 ms

flag.png

flag.png

428 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

505 ms

subs.png

subs.png

453 ms

z_stat.php

z_stat.php

2634 ms

518 ms

analytics.js

analytics.js

95 ms

ec.js

ec.js

30 ms

collect

collect

54 ms

collect

collect

208 ms

collect

collect

105 ms

collect

collect

242 ms

ga-audiences

ga-audiences

118 ms

ga-audiences

ga-audiences

100 ms

265 ms

stat.htm

stat.htm

931 ms

core.php

core.php

3176 ms

9.gif

9.gif

8391 ms

collect

collect

36 ms

collect

collect

22 ms

Accessibility Review

shineshines.com accessibility score

68

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

shineshines.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

shineshines.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shineshines.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Shineshines.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

shineshines.com

Open Graph description is not detected on the main page of Shineshines. 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: