Tools & Wizards About Us
420.co.uk screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

420.co.uk

420

Page Load Speed

824 ms in total

First Response

147 ms

Resources Loaded

541 ms

Page Rendered

136 ms

420.co.uk screenshot

About Website

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

Afternic is a one-stop site to buy domains, sell domains, and park domains. Experience the world's premiere domain marketplace and exchange reseller today.

Visit 420.co.uk

Key Findings

We analyzed 420.co.uk page load time and found that the first response time was 147 ms and then it took 677 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

420.co.uk performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

420.co.uk

147 ms

search

94 ms

uxcore2.min.css

43 ms

noheader.min.css

61 ms

f8fd8073f260b8e9.css

18 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 420.co.uk, 69% (29 requests) were made to Afternic.com and 21% (9 requests) were made to Img6.wsimg.com. The less responsive or slowest element that took the longest time to load (211 ms) relates to the external source Seal-central-northern-western-arizona.bbb.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.0 kB (28%)

Content Size

245.0 kB

After Optimization

177.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 420.co.uk main page is 245.0 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. 55% of websites need less resources to load. Images take 113.4 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 55.0 kB

  • Original 78.4 kB
  • After minification 78.3 kB
  • After compression 23.4 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 55.0 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 357 B

  • Original 113.4 kB
  • After minification 113.0 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. 420 images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 8.9 kB

  • Original 15.9 kB
  • After minification 15.4 kB
  • After compression 7.0 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 8.9 kB or 56% of the original size.

CSS Optimization

-10%

Potential reduce by 3.8 kB

  • Original 37.3 kB
  • After minification 37.1 kB
  • After compression 33.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. 420.co.uk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (70%)

Requests Now

40

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

420.co.uk

420.co.uk

147 ms

search

search

94 ms

uxcore2.min.css

uxcore2.min.css

43 ms

noheader.min.css

noheader.min.css

61 ms

f8fd8073f260b8e9.css

f8fd8073f260b8e9.css

18 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

36 ms

webpack-2ae0848a4992c193.js

webpack-2ae0848a4992c193.js

36 ms

main-2299c0cb7a00c050.js

main-2299c0cb7a00c050.js

35 ms

framework-f7ba292b22b03fed.js

framework-f7ba292b22b03fed.js

36 ms

_app-1b2ba2d41a2e89e1.js

_app-1b2ba2d41a2e89e1.js

51 ms

852-e33594a0a2e9a878.js

852-e33594a0a2e9a878.js

52 ms

446-0a5afffb8bd0f198.js

446-0a5afffb8bd0f198.js

51 ms

search-355e76238573036f.js

search-355e76238573036f.js

53 ms

_buildManifest.js

_buildManifest.js

54 ms

_ssgManifest.js

_ssgManifest.js

49 ms

_middlewareManifest.js

_middlewareManifest.js

53 ms

consent-main.js

consent-main.js

48 ms

tcc.min.js

tcc.min.js

49 ms

polyfill.min.js

polyfill.min.js

126 ms

uxcore2.min.js

uxcore2.min.js

99 ms

vendor~uxcore2.min.js

vendor~uxcore2.min.js

124 ms

heartbeat.js

heartbeat.js

49 ms

noheader.min.js

noheader.min.js

100 ms

aksb.min.js

aksb.min.js

110 ms

shadow-bodyfold.png

shadow-bodyfold.png

99 ms

blue-seal-96-50-godaddycomllc-22000169.png

blue-seal-96-50-godaddycomllc-22000169.png

211 ms

seal

seal

95 ms

sprites-home.png

sprites-home.png

83 ms

bg-subnav-15per-grey.png

bg-subnav-15per-grey.png

86 ms

icon-subnav-agent-green.png

icon-subnav-agent-green.png

83 ms

button-subnav-bg-bigblue.png

button-subnav-bg-bigblue.png

123 ms

button-subnav-bg-biggreen.png

button-subnav-bg-biggreen.png

80 ms

gd-logo.svg

gd-logo.svg

81 ms

bg-subnav-divider.png

bg-subnav-divider.png

111 ms

sprites-home.png

sprites-home.png

125 ms

shadow-wide-tuck.png

shadow-wide-tuck.png

104 ms

button-mainsearch-bg.png

button-mainsearch-bg.png

121 ms

shadow-subfooter.png

shadow-subfooter.png

132 ms

bg-footer-decoration.png

bg-footer-decoration.png

171 ms

bg-footer.png

bg-footer.png

172 ms

bg-footer-about.png

bg-footer-about.png

173 ms

shadow-footer-badges.png

shadow-footer-badges.png

172 ms

Accessibility Review

420.co.uk accessibility score

96

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

420.co.uk best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

420.co.uk SEO score

83

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

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

420.co.uk

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