Tools & Wizards About Us
poor-boy.co.uk screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

poor-boy.co.uk

Vintage Clothing | Poorboy Boutique Hull

Page Load Speed

7.2 sec in total

First Response

483 ms

Resources Loaded

6.3 sec

Page Rendered

438 ms

poor-boy.co.uk screenshot

About Website

Click here to check amazing Poorboy content. Otherwise, check out these important facts you probably never knew about poor-boy.co.uk

Premium hand-picked vintage clothing. Discover a wide range of clothing for men & women at Poorboy. From branded sweatshirts, jackets, knitwear, t-shirts, jeans, high-end garments, accessories & other...

Visit poor-boy.co.uk

Key Findings

We analyzed Poor-boy.co.uk page load time and found that the first response time was 483 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

poor-boy.co.uk performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value20.2 s

0/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value21.7 s

1/100

10%

Network Requests Diagram

poor-boy.co.uk

483 ms

www.poor-boy.co.uk

2676 ms

foundation.min.css

315 ms

app.css

172 ms

tiny-slider.css

39 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 82% of them (61 requests) were addressed to the original Poor-boy.co.uk, 7% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Poor-boy.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 942.8 kB (11%)

Content Size

8.8 MB

After Optimization

7.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Poor-boy.co.uk main page is 8.8 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. Only a small number of websites need less resources to load. Images take 8.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 105.2 kB

  • Original 130.2 kB
  • After minification 120.1 kB
  • After compression 25.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 105.2 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 798.1 kB

  • Original 8.3 MB
  • After minification 7.6 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. Poorboy images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 11.8 kB

  • Original 131.1 kB
  • After minification 131.1 kB
  • After compression 119.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-17%

Potential reduce by 27.6 kB

  • Original 162.7 kB
  • After minification 162.5 kB
  • After compression 135.1 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. Poor-boy.co.uk needs all CSS files to be minified and compressed as it can save up to 27.6 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (73%)

Requests Now

63

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

poor-boy.co.uk

poor-boy.co.uk

483 ms

www.poor-boy.co.uk

www.poor-boy.co.uk

2676 ms

foundation.min.css

foundation.min.css

315 ms

app.css

app.css

172 ms

tiny-slider.css

tiny-slider.css

39 ms

owl.carousel.min.css

owl.carousel.min.css

61 ms

owl.theme.default.min.css

owl.theme.default.min.css

59 ms

font-awesome.min.css

font-awesome.min.css

89 ms

fullmain.min.css

fullmain.min.css

107 ms

style.min.css

style.min.css

87 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

566 ms

wc-blocks-style.css

wc-blocks-style.css

118 ms

style.css

style.css

135 ms

gutenberg-blocks.css

gutenberg-blocks.css

613 ms

styles.css

styles.css

144 ms

public.css

public.css

635 ms

webfont.min.css

webfont.min.css

174 ms

public.min.css

public.min.css

198 ms

style.css

style.css

200 ms

icons.css

icons.css

407 ms

css

css

45 ms

woocommerce.css

woocommerce.css

225 ms

style.css

style.css

252 ms

jquery.min.js

jquery.min.js

281 ms

script.min.js

script.min.js

307 ms

sbi-scripts.min.js

sbi-scripts.min.js

339 ms

gtm4wp-woocommerce-enhanced.js

gtm4wp-woocommerce-enhanced.js

648 ms

email-decode.min.js

email-decode.min.js

352 ms

sbi-styles.min.css

sbi-styles.min.css

378 ms

index.js

index.js

402 ms

index.js

index.js

433 ms

stripe-handler-ng.js

stripe-handler-ng.js

758 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

457 ms

js.cookie.min.js

js.cookie.min.js

483 ms

woocommerce.min.js

woocommerce.min.js

508 ms

cart-fragments.min.js

cart-fragments.min.js

534 ms

njt-whatsapp.js

njt-whatsapp.js

562 ms

whatsapp-button.js

whatsapp-button.js

1148 ms

public.min.js

public.min.js

590 ms

api.js

api.js

67 ms

tiny-slider.js

tiny-slider.js

29 ms

navigation.min.js

navigation.min.js

613 ms

wp-polyfill.min.js

wp-polyfill.min.js

699 ms

index.js

index.js

612 ms

header-cart.min.js

header-cart.min.js

671 ms

footer.min.js

footer.min.js

851 ms

whatsapp-popup.js

whatsapp-popup.js

980 ms

owl.carousel.min.js

owl.carousel.min.js

643 ms

gtm.js

gtm.js

105 ms

I_Sell_1_125.png

I_Sell_1_125.png

235 ms

logo.svg

logo.svg

900 ms

poorboy-vintage-clothing-onlie.png

poorboy-vintage-clothing-onlie.png

667 ms

hilfiger.png

hilfiger.png

1558 ms

IMG_1169.jpg

IMG_1169.jpg

1138 ms

poorboy-0553.jpg

poorboy-0553.jpg

1526 ms

poorboy-2797.jpg

poorboy-2797.jpg

1701 ms

untitled-1397.jpg

untitled-1397.jpg

1229 ms

poorboy-2600.jpg

poorboy-2600.jpg

1459 ms

Screen-Shot-2021-06-07-at-10.23.25.png

Screen-Shot-2021-06-07-at-10.23.25.png

1617 ms

https___d1e00ek4ebabms.cloudfront.net_production_5752f2f5-be91-4299-b0e6-3e1178ed7d5a.jpg

https___d1e00ek4ebabms.cloudfront.net_production_5752f2f5-be91-4299-b0e6-3e1178ed7d5a.jpg

1628 ms

visit-1.jpg

visit-1.jpg

2297 ms

visit-2.jpg

visit-2.jpg

2245 ms

first-data-white.jpg

first-data-white.jpg

2200 ms

gtm.js

gtm.js

79 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf

28 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdr.ttf

46 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdr.ttf

52 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf

66 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdr.ttf

52 ms

bebas-regular.otf

bebas-regular.otf

1737 ms

fa-brands-400.woff

fa-brands-400.woff

1757 ms

fa-solid-900.woff

fa-solid-900.woff

2336 ms

sbi-sprite.png

sbi-sprite.png

1856 ms

recaptcha__en.js

recaptcha__en.js

139 ms

Accessibility Review

poor-boy.co.uk accessibility score

81

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

poor-boy.co.uk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

poor-boy.co.uk SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Poor-boy.co.uk 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 Poor-boy.co.uk 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

poor-boy.co.uk

Open Graph data is detected on the main page of Poorboy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: