Tools & Wizards About Us
fuzzdandy.co.uk screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

fuzzdandy.co.uk

Retro Clothing | Mens Flares | Womens Streetwear | Vintage

Page Load Speed

5.3 sec in total

First Response

785 ms

Resources Loaded

2.4 sec

Page Rendered

2.1 sec

fuzzdandy.co.uk screenshot

About Website

Click here to check amazing Fuzzdandy content. Otherwise, check out these important facts you probably never knew about fuzzdandy.co.uk

Fuzzdandy specialise in Mens and Womens indie, retro, streetwear & mod styles., supplying ITV, Sky, BBC.

Visit fuzzdandy.co.uk

Key Findings

We analyzed Fuzzdandy.co.uk page load time and found that the first response time was 785 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

fuzzdandy.co.uk performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value1.095

1/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

www.fuzzdandy.co.uk

785 ms

splide.min.css

26 ms

base.css

25 ms

buttons.css

28 ms

style.css

30 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 10% of them (6 requests) were addressed to the original Fuzzdandy.co.uk, 25% (15 requests) were made to 20.cdn.ekm.net and 19% (11 requests) were made to Files.ekmcdn.com. The less responsive or slowest element that took the longest time to load (896 ms) relates to the external source Files.ekmcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.6 kB (5%)

Content Size

5.3 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fuzzdandy.co.uk main page is 5.3 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. 50% of websites need less resources to load. Images take 5.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 192.5 kB

  • Original 219.3 kB
  • After minification 185.4 kB
  • After compression 26.8 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 34.0 kB, which is 15% 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 192.5 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 76.6 kB

  • Original 5.0 MB
  • After minification 4.9 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. Fuzzdandy images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.3 kB

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

CSS Optimization

-6%

Potential reduce by 3.3 kB

  • Original 51.8 kB
  • After minification 51.7 kB
  • After compression 48.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. Fuzzdandy.co.uk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (58%)

Requests Now

53

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.fuzzdandy.co.uk

www.fuzzdandy.co.uk

785 ms

splide.min.css

splide.min.css

26 ms

base.css

base.css

25 ms

buttons.css

buttons.css

28 ms

style.css

style.css

30 ms

blog_post.css

blog_post.css

32 ms

newsletter.css

newsletter.css

33 ms

css2

css2

40 ms

shopui.css

shopui.css

25 ms

css2

css2

59 ms

showdata-thumbnailhover.min.js

showdata-thumbnailhover.min.js

28 ms

showdata-thumbnailhover.css

showdata-thumbnailhover.css

32 ms

upsell-splide-init.min.js

upsell-splide-init.min.js

34 ms

softcart.min.css

softcart.min.css

34 ms

softcart.min.js

softcart.min.js

35 ms

historytracker.js

historytracker.js

35 ms

productimagebadge.css

productimagebadge.css

34 ms

productimagebadge.min.js

productimagebadge.min.js

34 ms

css

css

26 ms

gtm.js

gtm.js

152 ms

ga.js

ga.js

72 ms

fa-safe.css

fa-safe.css

27 ms

fuzzdandy-logo-2024.jpg

fuzzdandy-logo-2024.jpg

136 ms

newslettersignup.js

newslettersignup.js

7 ms

splide.min.js

splide.min.js

7 ms

scripts.js

scripts.js

10 ms

newsletterpopup.js

newsletterpopup.js

8 ms

shopui.js

shopui.js

7 ms

stats-global.js

stats-global.js

389 ms

gbp.svg

gbp.svg

108 ms

loading.png

loading.png

93 ms

facebook.svg

facebook.svg

102 ms

visa.png

visa.png

78 ms

maestro.png

maestro.png

71 ms

mastercard.png

mastercard.png

78 ms

delta.png

delta.png

78 ms

paypal.png

paypal.png

71 ms

MobBanner1Edit_1683813412.png

MobBanner1Edit_1683813412.png

93 ms

MobBanner2_1683813432.png

MobBanner2_1683813432.png

94 ms

USP-01_1683813356.svg

USP-01_1683813356.svg

433 ms

USP-02_1683813375.svg

USP-02_1683813375.svg

413 ms

%E2%80%94Pngtree%E2%80%94carton_delivery_5399771_1714467632.png

%E2%80%94Pngtree%E2%80%94carton_delivery_5399771_1714467632.png

93 ms

postman_1714468127.png

postman_1714468127.png

93 ms

IMG_5192_1711540833.JPG

IMG_5192_1711540833.JPG

896 ms

434142148_3675146286106717_7888639108667105689_n_1711541833.jpg

434142148_3675146286106717_7888639108667105689_n_1711541833.jpg

96 ms

IMG-8991_1711542057.JPG

IMG-8991_1711542057.JPG

845 ms

IMG_9517_1711542479.JPG

IMG_9517_1711542479.JPG

890 ms

no-p-img.png

no-p-img.png

77 ms

about-us.jpg

about-us.jpg

76 ms

twitter.svg

twitter.svg

164 ms

instagram.svg

instagram.svg

249 ms

blog.svg

blog.svg

333 ms

emailicon.svg

emailicon.svg

347 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7oUUsgNsFjTQpJ.woff

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7oUUsgNsFjTQpJ.woff

166 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7aUUsgNsFjTQpJ.woff

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7aUUsgNsFjTQpJ.woff

273 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj62UUsgNsFjTQpJ.woff

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj62UUsgNsFjTQpJ.woff

265 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj42VksgNsFjTQpJ.woff

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj42VksgNsFjTQpJ.woff

193 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj4PVksgNsFjTQpJ.woff

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj4PVksgNsFjTQpJ.woff

252 ms

__utm.gif

__utm.gif

30 ms

Accessibility Review

fuzzdandy.co.uk accessibility score

91

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fuzzdandy.co.uk best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fuzzdandy.co.uk SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 Fuzzdandy.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 Fuzzdandy.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

fuzzdandy.co.uk

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