Tools & Wizards About Us
fashionlondon.co screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fashionlondon.co

Loading...

Page Load Speed

2.4 sec in total

First Response

574 ms

Resources Loaded

1.6 sec

Page Rendered

199 ms

fashionlondon.co screenshot

About Website

Visit fashionlondon.co now to see the best up-to-date Fashionlondon content and also check out these interesting facts you probably never knew about fashionlondon.co

Visit fashionlondon.co

Key Findings

We analyzed Fashionlondon.co page load time and found that the first response time was 574 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

fashionlondon.co performance score

0

Network Requests Diagram

fashionlondon.co

574 ms

styles.css

105 ms

WOWButton.png

257 ms

logo.gif

278 ms

twitter.png

300 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 48% of them (14 requests) were addressed to the original Fashionlondon.co, 28% (8 requests) were made to Platform.twitter.com and 7% (2 requests) were made to Pha-media.com. The less responsive or slowest element that took the longest time to load (945 ms) belongs to the original domain Fashionlondon.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 99.2 kB (13%)

Content Size

741.2 kB

After Optimization

641.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fashionlondon.co main page is 741.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 671.5 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 6.4 kB

  • Original 9.5 kB
  • After minification 8.2 kB
  • After compression 3.0 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 1.3 kB, which is 14% 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 6.4 kB or 68% of the original size.

Image Optimization

-8%

Potential reduce by 55.0 kB

  • Original 671.5 kB
  • After minification 616.5 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. Fashionlondon images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

CSS Optimization

-79%

Potential reduce by 5.8 kB

  • Original 7.3 kB
  • After minification 5.3 kB
  • After compression 1.5 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. Fashionlondon.co needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

27

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fashionlondon.co

fashionlondon.co

574 ms

styles.css

styles.css

105 ms

WOWButton.png

WOWButton.png

257 ms

logo.gif

logo.gif

278 ms

twitter.png

twitter.png

300 ms

facebook.png

facebook.png

289 ms

pinterest.png

pinterest.png

298 ms

Fashion%20London%202016-01%20Web%20(1)_Page_01.jpg

Fashion%20London%202016-01%20Web%20(1)_Page_01.jpg

500 ms

thumb_about_n.jpg

thumb_about_n.jpg

562 ms

thumb_2_n.jpg

thumb_2_n.jpg

463 ms

thumb_edition_n.jpg

thumb_edition_n.jpg

677 ms

widgets.js

widgets.js

6 ms

analytics.js

analytics.js

25 ms

bg.jpg

bg.jpg

288 ms

bg_nav.gif

bg_nav.gif

420 ms

header-img_n.jpg

header-img_n.jpg

945 ms

black65.png

black65.png

547 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

30 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

32 ms

collect

collect

17 ms

syndication

syndication

104 ms

298415421432922112

298415421432922112

205 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

14 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

22 ms

WOWButton.png

WOWButton.png

339 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

3 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

3 ms

cFx8XkPn_normal.jpg

cFx8XkPn_normal.jpg

139 ms

jot.html

jot.html

2 ms

SEO Factors

fashionlondon.co SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fashionlondon.co 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Fashionlondon.co 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

fashionlondon.co

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