Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

22seconds.net

Computing - The UK's leading source for the analysis of business technology

Page Load Speed

4.5 sec in total

First Response

535 ms

Resources Loaded

3.1 sec

Page Rendered

891 ms

22seconds.net screenshot

About Website

Click here to check amazing 22 Seconds content. Otherwise, check out these important facts you probably never knew about 22seconds.net

Computing is the leading information resource for UK technology decision makers, providing the latest market news and hard-hitting opinion.

Visit 22seconds.net

Key Findings

We analyzed 22seconds.net page load time and found that the first response time was 535 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

22seconds.net performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value20.6 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.198

62/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

www.computing.co.uk

535 ms

launch-cc469565ed77.min.js

30 ms

gtm.js

61 ms

styles.css

197 ms

application-ebebbb5e1badfb22afb440bf86308f4f5f45fdc023c96fb638875ec32af5a3c2.css

105 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 22seconds.net, 13% (11 requests) were made to Cdn.privacy-mgmt.com and 11% (10 requests) were made to Securepubads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Computing.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 229.6 kB (7%)

Content Size

3.4 MB

After Optimization

3.2 MB

In fact, the total size of 22seconds.net main page is 3.4 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. 80% 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 99.3 kB

  • Original 126.6 kB
  • After minification 125.6 kB
  • After compression 27.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 99.3 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 14.9 kB

  • Original 2.3 MB
  • After minification 2.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. 22 Seconds images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 115.3 kB

  • Original 865.3 kB
  • After minification 865.2 kB
  • After compression 750.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 115.3 kB or 13% of the original size.

CSS Optimization

-0%

Potential reduce by 8 B

  • Original 49.7 kB
  • After minification 49.7 kB
  • After compression 49.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. 22seconds.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 40 (48%)

Requests Now

83

After Optimization

43

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

Accessibility Review

22seconds.net accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

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

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

22seconds.net best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

22seconds.net SEO score

84

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

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 22seconds.net 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 22seconds.net 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

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