Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

23seconds.be

23:Seconds - Javascript Competence Center / Product Center

Page Load Speed

3.6 sec in total

First Response

425 ms

Resources Loaded

2.7 sec

Page Rendered

536 ms

23seconds.be screenshot

About Website

Click here to check amazing 23 Seconds content for Belgium. Otherwise, check out these important facts you probably never knew about 23seconds.be

23:Seconds, a javascript competence and product center devoted to modern, realtime and reactive applications using web technologies. Javascript as a true cross-device, cross-platform development platf...

Visit 23seconds.be

Key Findings

We analyzed 23seconds.be page load time and found that the first response time was 425 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

23seconds.be performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value17.8 s

0/100

10%

TBT (Total Blocking Time)

Value15,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.35

31/100

15%

TTI (Time to Interactive)

Value26.4 s

0/100

10%

Network Requests Diagram

23seconds.be

425 ms

f69db5500838f11188617bdd48c6f2c69a540733.css

200 ms

1ccb2e80de06711fd3c16f2d3f12adb3b8b55403.js

849 ms

font-awesome.min.css

190 ms

css

152 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 74% of them (26 requests) were addressed to the original 23seconds.be, 11% (4 requests) were made to Fonts.gstatic.com and 9% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (849 ms) belongs to the original domain 23seconds.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 94.7 kB (33%)

Content Size

285.0 kB

After Optimization

190.3 kB

In fact, the total size of 23seconds.be main page is 285.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. 35% of websites need less resources to load. Javascripts take 133.4 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 43.5 kB

  • Original 61.9 kB
  • After minification 52.9 kB
  • After compression 18.5 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 9.1 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 43.5 kB or 70% of the original size.

Image Optimization

-5%

Potential reduce by 4.5 kB

  • Original 89.7 kB
  • After minification 85.2 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. 23 Seconds images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 46.8 kB

  • Original 133.4 kB
  • After minification 133.4 kB
  • After compression 86.6 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 46.8 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (39%)

Requests Now

28

After Optimization

17

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 23 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 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

23seconds.be accessibility score

78

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

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

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

Best Practices

23seconds.be 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

23seconds.be SEO score

85

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

High

robots.txt is not valid

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 23seconds.be 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 23seconds.be 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 23 Seconds. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: