Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

hotfrog.be

Het Voorportaal | Altijd het eerste zakelijke nieuws

Page Load Speed

1 sec in total

First Response

259 ms

Resources Loaded

631 ms

Page Rendered

127 ms

hotfrog.be screenshot

About Website

Visit hotfrog.be now to see the best up-to-date Hotfrog content and also check out these interesting facts you probably never knew about hotfrog.be

Visit hotfrog.be

Key Findings

We analyzed Hotfrog.be page load time and found that the first response time was 259 ms and then it took 758 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

hotfrog.be performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value2,750 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

hotfrog.be

259 ms

jquery.min.js

202 ms

onlydomains.png

131 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that all of those requests were addressed to Hotfrog.be and no external sources were called. The less responsive or slowest element that took the longest time to load (259 ms) belongs to the original domain Hotfrog.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.9 kB (63%)

Content Size

100.6 kB

After Optimization

36.8 kB

In fact, the total size of Hotfrog.be main page is 100.6 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. Only 5% of websites need less resources to load. Javascripts take 96.0 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 1.4 kB

  • Original 2.4 kB
  • After minification 2.2 kB
  • After compression 982 B

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 1.4 kB or 59% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.3 kB
  • After minification 2.3 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. Hotfrog images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 62.5 kB

  • Original 96.0 kB
  • After minification 96.0 kB
  • After compression 33.5 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 62.5 kB or 65% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hotfrog. According to our analytics all requests are already optimized.

Accessibility Review

hotfrog.be accessibility score

82

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

hotfrog.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hotfrog.be SEO score

85

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

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