Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

cuttingedge.be

Cutting Edge – Messcherp door Cultuur en Media – webzine

Page Load Speed

4.7 sec in total

First Response

288 ms

Resources Loaded

4.2 sec

Page Rendered

253 ms

cuttingedge.be screenshot

About Website

Welcome to cuttingedge.be homepage info - get ready to check Cutting Edge best content for Belgium right away, or after learning these important things about cuttingedge.be

Messcherp door cultuur en media, zo snijden onze redacteurs dagelijks. Van boeken en strips, muziek en theater tot films en series.

Visit cuttingedge.be

Key Findings

We analyzed Cuttingedge.be page load time and found that the first response time was 288 ms and then it took 4.4 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

cuttingedge.be performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value20.7 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value330 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.382

27/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

cuttingedge.be

288 ms

www.cuttingedge.be

389 ms

6ee0fea4-c602-494e-8426-3c066d0115a0.css

59 ms

system.base.css

168 ms

system.menus.css

176 ms

Our browser made a total of 187 requests to load all elements on the main page. We found that 49% of them (91 requests) were addressed to the original Cuttingedge.be, 8% (15 requests) were made to Pixel.rubiconproject.com and 4% (7 requests) were made to Ads-pebblemedia.adhese.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Cuttingedge.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (48%)

Content Size

2.3 MB

After Optimization

1.2 MB

In fact, the total size of Cuttingedge.be main page is 2.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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 111.2 kB

  • Original 144.2 kB
  • After minification 138.0 kB
  • After compression 33.0 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 111.2 kB or 77% of the original size.

Image Optimization

-12%

Potential reduce by 109.4 kB

  • Original 912.5 kB
  • After minification 803.1 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. Obviously, Cutting Edge needs image optimization as it can save up to 109.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 745.4 kB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 341.8 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 745.4 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 153.6 kB

  • Original 185.3 kB
  • After minification 150.2 kB
  • After compression 31.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. Cuttingedge.be needs all CSS files to be minified and compressed as it can save up to 153.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 104 (60%)

Requests Now

172

After Optimization

68

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

Accessibility Review

cuttingedge.be accessibility score

80

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

High

Form elements do not have associated labels

High

Links do not have a discernible 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.

Best Practices

cuttingedge.be best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

cuttingedge.be SEO score

99

Search Engine Optimization Advices

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cuttingedge.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Cuttingedge.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 description is not detected on the main page of Cutting Edge. 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: