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

Report Summary

  • 17

    Performance

    Renders faster than
    33% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

poor-boy.co.uk

Poorboy Boutique Vintage Clothing | Vintage Clothing Store Hull

Page Load Speed

28.2 sec in total

First Response

231 ms

Resources Loaded

22.2 sec

Page Rendered

5.7 sec

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

Come down to the Poorboy Boutique Vintage Clothing Store at No.17 Humber St, Hull HU1 1TH. In store we have a large range of vintage clothing.

Visit poor-boy.co.uk

Key Findings

We analyzed Poor-boy.co.uk page load time and found that the first response time was 231 ms and then it took 28 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

poor-boy.co.uk performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value48.0 s

0/100

25%

SI (Speed Index)

Value24.8 s

0/100

10%

TBT (Total Blocking Time)

Value14,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value47.5 s

0/100

10%

Network Requests Diagram

poor-boy.co.uk

231 ms

poor-boy.co.uk

1427 ms

gtm.js

173 ms

js

255 ms

foundation.min.css

159 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 74% of them (64 requests) were addressed to the original Poor-boy.co.uk, 6% (5 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Marketplace.asos.com.

Page Optimization Overview & Recommendations

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

Content Size

6.0 MB

After Optimization

5.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Poor-boy.co.uk main page is 6.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 74.7 kB

  • Original 92.2 kB
  • After minification 81.7 kB
  • After compression 17.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 10.6 kB, which is 11% 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 74.7 kB or 81% of the original size.

Image Optimization

-12%

Potential reduce by 689.6 kB

  • Original 5.8 MB
  • After minification 5.1 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. Obviously, Poorboy needs image optimization as it can save up to 689.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 478 B

  • Original 32.2 kB
  • After minification 32.2 kB
  • After compression 31.8 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

-2%

Potential reduce by 862 B

  • Original 49.6 kB
  • After minification 49.6 kB
  • After compression 48.7 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 52 (69%)

Requests Now

75

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 75 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 32 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

231 ms

poor-boy.co.uk

poor-boy.co.uk

1427 ms

gtm.js

gtm.js

173 ms

js

js

255 ms

foundation.min.css

foundation.min.css

159 ms

app.css

app.css

255 ms

tiny-slider.css

tiny-slider.css

166 ms

owl.carousel.min.css

owl.carousel.min.css

109 ms

owl.theme.default.min.css

owl.theme.default.min.css

204 ms

font-awesome.min.css

font-awesome.min.css

246 ms

fullmain.min.css

fullmain.min.css

380 ms

style.min.css

style.min.css

665 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

460 ms

wc-blocks-style.css

wc-blocks-style.css

463 ms

style.css

style.css

492 ms

gutenberg-blocks.css

gutenberg-blocks.css

438 ms

styles.css

styles.css

457 ms

public.css

public.css

752 ms

webfont.min.css

webfont.min.css

755 ms

public.min.css

public.min.css

664 ms

style.css

style.css

607 ms

icons.css

icons.css

613 ms

css

css

156 ms

woocommerce.css

woocommerce.css

654 ms

style.css

style.css

611 ms

jquery.min.js

jquery.min.js

880 ms

sbi-scripts.min.js

sbi-scripts.min.js

929 ms

email-decode.min.js

email-decode.min.js

646 ms

sbi-styles.min.css

sbi-styles.min.css

724 ms

index.js

index.js

715 ms

index.js

index.js

819 ms

stripe-handler-ng.js

stripe-handler-ng.js

831 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

855 ms

add-to-cart.min.js

add-to-cart.min.js

779 ms

js.cookie.min.js

js.cookie.min.js

837 ms

woocommerce.min.js

woocommerce.min.js

1002 ms

cart-fragments.min.js

cart-fragments.min.js

1272 ms

njt-whatsapp.js

njt-whatsapp.js

1287 ms

whatsapp-button.js

whatsapp-button.js

1273 ms

public.min.js

public.min.js

907 ms

navigation.min.js

navigation.min.js

1348 ms

api.js

api.js

174 ms

tiny-slider.js

tiny-slider.js

127 ms

skip-link-focus-fix.min.js

skip-link-focus-fix.min.js

1284 ms

pep.min.js

pep.min.js

1254 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1203 ms

wp-polyfill.min.js

wp-polyfill.min.js

1159 ms

analytics.js

analytics.js

302 ms

js

js

229 ms

index.js

index.js

991 ms

header-cart.min.js

header-cart.min.js

956 ms

footer.min.js

footer.min.js

979 ms

whatsapp-popup.js

whatsapp-popup.js

925 ms

owl.carousel.min.js

owl.carousel.min.js

926 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

902 ms

collect

collect

86 ms

collect

collect

85 ms

collect

collect

71 ms

collect

collect

91 ms

ga-audiences

ga-audiences

60 ms

ga-audiences

ga-audiences

36 ms

I_Sell_1_125.png

I_Sell_1_125.png

19602 ms

logo.svg

logo.svg

355 ms

poorboy-vintage-clothing-onlie.png

poorboy-vintage-clothing-onlie.png

1275 ms

hilfiger.png

hilfiger.png

1527 ms

IMG_1169.jpg

IMG_1169.jpg

700 ms

vintage-levis-501-blue-jeans-poorboy-1274.jpg

vintage-levis-501-blue-jeans-poorboy-1274.jpg

510 ms

vintage-puffer-poorboy-0816.jpg

vintage-puffer-poorboy-0816.jpg

1107 ms

vintage-leather-jacket-racing-poorboy-0787.jpg

vintage-leather-jacket-racing-poorboy-0787.jpg

910 ms

vintage-leather-jacket-tassel-poorboy-0685.jpg

vintage-leather-jacket-tassel-poorboy-0685.jpg

1104 ms

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

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

911 ms

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

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

1100 ms

visit-1.jpg

visit-1.jpg

1100 ms

visit-2.jpg

visit-2.jpg

1110 ms

first-data-white.jpg

first-data-white.jpg

1109 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7gujVj9w.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7gujVj9w.ttf

119 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdr3cOWxw.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdr3cOWxw.ttf

189 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdr3cOWxw.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdr3cOWxw.ttf

361 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr3cOWxw.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr3cOWxw.ttf

361 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdr3cOWxw.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdr3cOWxw.ttf

362 ms

bebas-regular.otf

bebas-regular.otf

783 ms

fa-brands-400.woff

fa-brands-400.woff

946 ms

fa-solid-900.woff

fa-solid-900.woff

946 ms

recaptcha__en.js

recaptcha__en.js

499 ms

1f680.svg

1f680.svg

449 ms

poor-boy.co.uk

poor-boy.co.uk

1429 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: