Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 70% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

hockey.be

KBHB - VHL - LFH - widget - Hockey Belgium

Page Load Speed

5.5 sec in total

First Response

1.2 sec

Resources Loaded

3.8 sec

Page Rendered

386 ms

hockey.be screenshot

About Website

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

Visit hockey.be

Key Findings

We analyzed Hockey.be page load time and found that the first response time was 1.2 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

hockey.be performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value8,890 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.682

8/100

15%

TTI (Time to Interactive)

Value27.4 s

0/100

10%

Network Requests Diagram

www.hockey.be

1219 ms

ddlevelsmenu.js

439 ms

website.css

508 ms

image_rotator.css

308 ms

ddlevelsmenu-base.css

220 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 89% of them (82 requests) were addressed to the original Hockey.be, 11% (10 requests) were made to Hockeynews.be. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Hockey.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (31%)

Content Size

3.9 MB

After Optimization

2.7 MB

In fact, the total size of Hockey.be main page is 3.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. 35% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 39.1 kB

  • Original 46.6 kB
  • After minification 46.5 kB
  • After compression 7.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. 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 39.1 kB or 84% of the original size.

Image Optimization

-18%

Potential reduce by 558.4 kB

  • Original 3.0 MB
  • After minification 2.5 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, Hockey needs image optimization as it can save up to 558.4 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 535.8 kB

  • Original 716.1 kB
  • After minification 656.1 kB
  • After compression 180.4 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 535.8 kB or 75% of the original size.

CSS Optimization

-86%

Potential reduce by 86.8 kB

  • Original 100.6 kB
  • After minification 74.4 kB
  • After compression 13.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. Hockey.be needs all CSS files to be minified and compressed as it can save up to 86.8 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

91

After Optimization

63

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

Accessibility Review

hockey.be accessibility score

88

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

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.

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

hockey.be best practices score

83

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

Browser errors were logged to the console

SEO Factors

hockey.be SEO score

89

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

    N/A

  • Encoding

    LATIN1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hockey.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch 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 Hockey.be main page’s claimed encoding is latin1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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