Tools & Wizards About Us
twenty-o-two.co.uk screenshot

Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

twenty-o-two.co.uk

twenty-o-two • London | New Website from £999 | SEO

Page Load Speed

2 sec in total

First Response

390 ms

Resources Loaded

1.4 sec

Page Rendered

185 ms

twenty-o-two.co.uk screenshot

About Website

Click here to check amazing Twenty O Two content. Otherwise, check out these important facts you probably never knew about twenty-o-two.co.uk

London based digital company that keep pushing the limits of the {im}possible. Web & App development, Digital Design, SEO. Digital marketing strategies for every business.

Visit twenty-o-two.co.uk

Key Findings

We analyzed Twenty-o-two.co.uk page load time and found that the first response time was 390 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

twenty-o-two.co.uk performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

71/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

twenty-o-two.co.uk

390 ms

normalize.css

90 ms

main.css

174 ms

hamburgers.min.css

175 ms

css

39 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 77% of them (34 requests) were addressed to the original Twenty-o-two.co.uk, 9% (4 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (751 ms) belongs to the original domain Twenty-o-two.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 568.8 kB (30%)

Content Size

1.9 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Twenty-o-two.co.uk main page is 1.9 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.8 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 5.7 kB

  • Original 8.0 kB
  • After minification 7.6 kB
  • After compression 2.3 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 5.7 kB or 71% of the original size.

Image Optimization

-29%

Potential reduce by 527.8 kB

  • Original 1.8 MB
  • After minification 1.3 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, Twenty O Two needs image optimization as it can save up to 527.8 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 32.1 kB

  • Original 53.4 kB
  • After minification 53.4 kB
  • After compression 21.3 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 32.1 kB or 60% of the original size.

CSS Optimization

-41%

Potential reduce by 3.3 kB

  • Original 8.1 kB
  • After minification 7.4 kB
  • After compression 4.8 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. Twenty-o-two.co.uk needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (18%)

Requests Now

38

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

twenty-o-two.co.uk

twenty-o-two.co.uk

390 ms

normalize.css

normalize.css

90 ms

main.css

main.css

174 ms

hamburgers.min.css

hamburgers.min.css

175 ms

css

css

39 ms

vue.js

vue.js

37 ms

main.js

main.js

200 ms

js

js

75 ms

logo-black.png

logo-black.png

255 ms

email.png

email.png

257 ms

linked.png

linked.png

256 ms

insta.png

insta.png

296 ms

oct1.jpg

oct1.jpg

195 ms

oct2.jpg

oct2.jpg

275 ms

oct3.jpg

oct3.jpg

213 ms

c00001.jpg

c00001.jpg

323 ms

c0001.jpg

c0001.jpg

322 ms

c001.jpg

c001.jpg

319 ms

c01.jpg

c01.jpg

277 ms

c02.jpg

c02.jpg

315 ms

c1.jpg

c1.jpg

361 ms

c2.jpg

c2.jpg

448 ms

c3.jpg

c3.jpg

517 ms

c4.jpg

c4.jpg

573 ms

c5.jpg

c5.jpg

523 ms

c6.jpg

c6.jpg

523 ms

c7.jpg

c7.jpg

530 ms

c8.jpg

c8.jpg

619 ms

c9.jpg

c9.jpg

719 ms

c10.jpg

c10.jpg

624 ms

c11.jpg

c11.jpg

725 ms

c12.jpg

c12.jpg

701 ms

c13.jpg

c13.jpg

658 ms

c14.jpg

c14.jpg

703 ms

c15.jpg

c15.jpg

726 ms

c16.jpg

c16.jpg

745 ms

dummy

dummy

751 ms

js

js

63 ms

analytics.js

analytics.js

30 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

79 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

79 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

84 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

85 ms

collect

collect

41 ms

Accessibility Review

twenty-o-two.co.uk accessibility score

72

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

twenty-o-two.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

SEO Factors

twenty-o-two.co.uk SEO score

92

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Twenty-o-two.co.uk can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Twenty-o-two.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

twenty-o-two.co.uk

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