Tools & Wizards About Us
prettygreen.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

prettygreen.com

Pretty Green | Official Pretty Green Online Store

Page Load Speed

4.8 sec in total

First Response

216 ms

Resources Loaded

3.1 sec

Page Rendered

1.4 sec

prettygreen.com screenshot

About Website

Visit prettygreen.com now to see the best up-to-date Pretty Green content for United Kingdom and also check out these interesting facts you probably never knew about prettygreen.com

Official Pretty Green Online Store. Shop Clothing, Accessories & Footwear With A Modern Twist. Explore The Latest Pretty Green Arrivals & Collections Today.

Visit prettygreen.com

Key Findings

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

Performance Metrics

prettygreen.com performance score

0

Network Requests Diagram

prettygreen.com

216 ms

www.prettygreen.com

737 ms

3558930950.js

18 ms

normalize.css

179 ms

foundation.css

234 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 62% of them (40 requests) were addressed to the original Prettygreen.com, 8% (5 requests) were made to S3-eu-west-1.amazonaws.com and 6% (4 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (824 ms) belongs to the original domain Prettygreen.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 858.8 kB (36%)

Content Size

2.4 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 42.7 kB

  • Original 52.3 kB
  • After minification 39.4 kB
  • After compression 9.6 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 12.9 kB, which is 25% 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 42.7 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 24.2 kB

  • Original 1.3 MB
  • After minification 1.2 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. Pretty Green images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 486.9 kB

  • Original 719.9 kB
  • After minification 675.4 kB
  • After compression 233.1 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 486.9 kB or 68% of the original size.

CSS Optimization

-88%

Potential reduce by 305.0 kB

  • Original 347.6 kB
  • After minification 280.6 kB
  • After compression 42.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. Prettygreen.com needs all CSS files to be minified and compressed as it can save up to 305.0 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (43%)

Requests Now

56

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prettygreen.com

prettygreen.com

216 ms

www.prettygreen.com

www.prettygreen.com

737 ms

3558930950.js

3558930950.js

18 ms

normalize.css

normalize.css

179 ms

foundation.css

foundation.css

234 ms

app-only.css

app-only.css

279 ms

slick.css

slick.css

163 ms

font-awesome.min.css

font-awesome.min.css

164 ms

css

css

178 ms

css

css

178 ms

stylesheet.css

stylesheet.css

179 ms

app-fix-v1.css

app-fix-v1.css

179 ms

jquery-1.7.min.js

jquery-1.7.min.js

390 ms

jquery-ui-1.8.2.custom.min.js

jquery-ui-1.8.2.custom.min.js

566 ms

jqModal.js

jqModal.js

277 ms

modernizr.js

modernizr.js

384 ms

new_common.js

new_common.js

347 ms

slick.min.js

slick.min.js

160 ms

foundation.min.js

foundation.min.js

824 ms

production.js

production.js

345 ms

app.js

app.js

381 ms

ld.js

ld.js

159 ms

conversion.js

conversion.js

157 ms

ie8.js

ie8.js

449 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

401 ms

analytics.js

analytics.js

123 ms

ns-large-home.jpg.jpg

ns-large-home.jpg.jpg

282 ms

pg-logo.png

pg-logo.png

228 ms

cart.png

cart.png

216 ms

wk-1619-small-banner-4.jpg

wk-1619-small-banner-4.jpg

394 ms

wk-1619-small-banner-3.jpg

wk-1619-small-banner-3.jpg

418 ms

wk-1620-small-banner-1.jpg

wk-1620-small-banner-1.jpg

217 ms

wk-1619-third-banner-1.jpg

wk-1619-third-banner-1.jpg

392 ms

wk-1620-bottom-banner-1.jpg

wk-1620-bottom-banner-1.jpg

635 ms

GRXG-1191-8545-KHAKI_1_t_w250_h250.jpg

GRXG-1191-8545-KHAKI_1_t_w250_h250.jpg

216 ms

GRXG52748522-SKY_1_t_w250_h250.jpg

GRXG52748522-SKY_1_t_w250_h250.jpg

391 ms

BRXG11688344-BLACK_1_t_w250_h250.jpg

BRXG11688344-BLACK_1_t_w250_h250.jpg

390 ms

BRXG11638340-BLK_1_t_w250_h250.jpg

BRXG11638340-BLK_1_t_w250_h250.jpg

391 ms

BRXG93337303-WHITE_1_t_w250_h250.jpg

BRXG93337303-WHITE_1_t_w250_h250.jpg

392 ms

BRXG93287298-WHITE_1_t_w250_h250.jpg

BRXG93287298-WHITE_1_t_w250_h250.jpg

391 ms

BRXG93707311-GRY_1_t_w250_h250.jpg

BRXG93707311-GRY_1_t_w250_h250.jpg

414 ms

BRXG93287298-CHAR_1_t_w250_h250.jpg

BRXG93287298-CHAR_1_t_w250_h250.jpg

413 ms

BRXG93717312-GRY_1_t_w250_h250.jpg

BRXG93717312-GRY_1_t_w250_h250.jpg

632 ms

BRXG93297299-GRY_1_t_w250_h250.jpg

BRXG93297299-GRY_1_t_w250_h250.jpg

414 ms

BRXG93297299-BLK_1_t_w250_h250.jpg

BRXG93297299-BLK_1_t_w250_h250.jpg

630 ms

BRXG52308347-BLUE_1_t_w250_h250.jpg

BRXG52308347-BLUE_1_t_w250_h250.jpg

628 ms

BRXG52298346-WHITE_1_t_w250_h250.jpg

BRXG52298346-WHITE_1_t_w250_h250.jpg

655 ms

BRXG52328349-BLUE_1_t_w250_h250.jpg

BRXG52328349-BLUE_1_t_w250_h250.jpg

655 ms

BRXG93327302-WHITE_1_t_w250_h250.jpg

BRXG93327302-WHITE_1_t_w250_h250.jpg

655 ms

ss16-new-arrivals.jpg

ss16-new-arrivals.jpg

376 ms

ss16-coats.jpg

ss16-coats.jpg

376 ms

ss16-polos.jpg

ss16-polos.jpg

377 ms

ss16-shirts.jpg

ss16-shirts.jpg

376 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

121 ms

ec.js

ec.js

142 ms

collect

collect

216 ms

vfr.js

vfr.js

210 ms

collect

collect

85 ms

pg-linearlogo.png

pg-linearlogo.png

79 ms

event

event

44 ms

39 ms

slick.woff

slick.woff

13 ms

event

event

175 ms

ajax-loader.gif

ajax-loader.gif

10 ms

56 ms

SEO Factors

prettygreen.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prettygreen.com 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 Prettygreen.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

prettygreen.com

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