Tools & Wizards About Us
playn.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

playn.com

PLAYN - Frames and Lenses Straight from the Makers

Page Load Speed

17.7 sec in total

First Response

1.2 sec

Resources Loaded

16.2 sec

Page Rendered

342 ms

playn.com screenshot

About Website

Visit playn.com now to see the best up-to-date PLAYN content and also check out these interesting facts you probably never knew about playn.com

We design and produce our own eyewear collection and deliver worldwide straight out of our lab.

Visit playn.com

Key Findings

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

Performance Metrics

playn.com performance score

0

Network Requests Diagram

playn.com

1153 ms

www.playn.com

1236 ms

beo1hdd.js

306 ms

d35e05aa44be139b681049c5f7486d94.css

559 ms

d9d49393d2bf4d7f6a6a96254a9a2d2b.js

2619 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 71% of them (50 requests) were addressed to the original Playn.com, 6% (4 requests) were made to Wedoasia.wufoo.com and 4% (3 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (6.9 sec) belongs to the original domain Playn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 727.5 kB (37%)

Content Size

1.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Playn.com main page is 1.9 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 49.6 kB

  • Original 59.7 kB
  • After minification 56.0 kB
  • After compression 10.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 49.6 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 44.5 kB

  • Original 1.0 MB
  • After minification 995.1 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. PLAYN images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 557.0 kB

  • Original 755.9 kB
  • After minification 643.6 kB
  • After compression 199.0 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 557.0 kB or 74% of the original size.

CSS Optimization

-82%

Potential reduce by 76.4 kB

  • Original 93.7 kB
  • After minification 81.3 kB
  • After compression 17.3 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. Playn.com needs all CSS files to be minified and compressed as it can save up to 76.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (22%)

Requests Now

68

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

playn.com

playn.com

1153 ms

www.playn.com

www.playn.com

1236 ms

beo1hdd.js

beo1hdd.js

306 ms

d35e05aa44be139b681049c5f7486d94.css

d35e05aa44be139b681049c5f7486d94.css

559 ms

d9d49393d2bf4d7f6a6a96254a9a2d2b.js

d9d49393d2bf4d7f6a6a96254a9a2d2b.js

2619 ms

12080698_888066897913668_1543019934_n.jpg

12080698_888066897913668_1543019934_n.jpg

493 ms

11374182_766412866804376_1374609067_n.jpg

11374182_766412866804376_1374609067_n.jpg

682 ms

12080471_439442849573030_564227185_n.jpg

12080471_439442849573030_564227185_n.jpg

860 ms

vista-youtube-1@2x.jpg

vista-youtube-1@2x.jpg

1681 ms

vista-youtube-2@2x.jpg

vista-youtube-2@2x.jpg

2432 ms

vista-youtube-3@2x.jpg

vista-youtube-3@2x.jpg

2506 ms

visa.png

visa.png

563 ms

mastercard.png

mastercard.png

565 ms

fedex.png

fedex.png

565 ms

paypal.png

paypal.png

1124 ms

logo-short.png

logo-short.png

1124 ms

ga.js

ga.js

21 ms

true

true

250 ms

icons.png

icons.png

1125 ms

tryon-realsize-70.png

tryon-realsize-70.png

2064 ms

all.js

all.js

96 ms

__utm.gif

__utm.gif

52 ms

arrow-left.png

arrow-left.png

1918 ms

arrow-right.png

arrow-right.png

2011 ms

instagram.png

instagram.png

2329 ms

youtube.png

youtube.png

2625 ms

db_helvethaica_x-webfont.woff

db_helvethaica_x-webfont.woff

3451 ms

db_helvethaica_x_bd-webfont.woff

db_helvethaica_x_bd-webfont.woff

3620 ms

9807.js

9807.js

58 ms

david_1.png

david_1.png

2842 ms

icon_barbey_1.png

icon_barbey_1.png

3042 ms

icon_rashad_1.png

icon_rashad_1.png

2908 ms

icon_grafica_1.png

icon_grafica_1.png

3329 ms

icon_wit_1.png

icon_wit_1.png

3512 ms

icon_loomit_1.png

icon_loomit_1.png

3626 ms

icon_bajka_1.png

icon_bajka_1.png

3670 ms

icon_shintaro_1.png

icon_shintaro_1.png

3888 ms

icon_deenesh_1.png

icon_deenesh_1.png

3967 ms

icon_felice_1.png

icon_felice_1.png

4071 ms

icon_jill_1.png

icon_jill_1.png

4136 ms

icon_sally_1.png

icon_sally_1.png

4510 ms

icon_sarah_1.png

icon_sarah_1.png

4539 ms

icon_huber_1.png

icon_huber_1.png

4479 ms

icon_marques_1.png

icon_marques_1.png

4803 ms

icon_jollyjay_1.png

icon_jollyjay_1.png

4647 ms

icon_djcc_1.png

icon_djcc_1.png

4697 ms

icon_eric_1.png

icon_eric_1.png

5036 ms

icon_ron_1.png

icon_ron_1.png

5086 ms

domonkos_1.png

domonkos_1.png

5135 ms

139 ms

xd_arbiter.php

xd_arbiter.php

82 ms

xd_arbiter.php

xd_arbiter.php

135 ms

index.0266.css

index.0266.css

173 ms

theme.css

theme.css

165 ms

beo1hdd.js

beo1hdd.js

128 ms

dynamic.0266.js

dynamic.0266.js

469 ms

playn.wufoo.newsletter.css

playn.wufoo.newsletter.css

4850 ms

keng_1.png

keng_1.png

4923 ms

logo.png

logo.png

5022 ms

5113601842c8f50c5627b8f5fdf1b9d2.jpg

5113601842c8f50c5627b8f5fdf1b9d2.jpg

6780 ms

c9f76cb6cbaeb1e729cdc3631ee305c3.jpg

c9f76cb6cbaeb1e729cdc3631ee305c3.jpg

6436 ms

83bde2de0edc72144411fca264e2adde.jpg

83bde2de0edc72144411fca264e2adde.jpg

6923 ms

frames.jpg

frames.jpg

5490 ms

lenses.jpg

lenses.jpg

4970 ms

stores.jpg

stores.jpg

5752 ms

bg-text.gif

bg-text.gif

2716 ms

xd_arbiter.php

xd_arbiter.php

37 ms

like.php

like.php

124 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

133 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

145 ms

SEO Factors

playn.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Playn.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Playn.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

playn.com

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