Tools & Wizards About Us
thefork.be screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

thefork.be

TheFork - Réservez dans les meilleurs restaurants de Belgique

Page Load Speed

2.3 sec in total

First Response

200 ms

Resources Loaded

1.7 sec

Page Rendered

413 ms

thefork.be screenshot

About Website

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

Avec TheFork : choisissez et réservez gratuitement dans les meilleurs restaurants de votre ville. Profitez aussi des promotions sur une sélection de restaurants !

Visit thefork.be

Key Findings

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

Performance Metrics

thefork.be performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value2,410 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.127

82/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

thefork.be

200 ms

www.thefork.be

376 ms

main.css

112 ms

homepage.css

90 ms

head.js

121 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Thefork.be, 29% (13 requests) were made to A.tfstatic.com and 22% (10 requests) were made to U.tfstatic.com. The less responsive or slowest element that took the longest time to load (391 ms) relates to the external source U.tfstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (55%)

Content Size

3.1 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thefork.be main page is 3.1 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. 75% 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. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 424.6 kB

  • Original 510.7 kB
  • After minification 508.2 kB
  • After compression 86.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 424.6 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 67.5 kB

  • Original 985.8 kB
  • After minification 918.4 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. The Fork images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 745.0 kB

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

CSS Optimization

-86%

Potential reduce by 501.8 kB

  • Original 583.1 kB
  • After minification 582.1 kB
  • After compression 81.3 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. Thefork.be needs all CSS files to be minified and compressed as it can save up to 501.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (51%)

Requests Now

37

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thefork.be

thefork.be

200 ms

www.thefork.be

www.thefork.be

376 ms

main.css

main.css

112 ms

homepage.css

homepage.css

90 ms

head.js

head.js

121 ms

2092620231.js

2092620231.js

120 ms

satelliteLib-3a537865a7a1019077c112febd0050243be74e27.js

satelliteLib-3a537865a7a1019077c112febd0050243be74e27.js

145 ms

bundle.js

bundle.js

243 ms

national_homepage.js

national_homepage.js

71 ms

css

css

70 ms

geo2.js

geo2.js

67 ms

event

event

32 ms

mbox-contents-270fc62b6c29acb02bbaf8ef5be772b78ee24b4f.js

mbox-contents-270fc62b6c29acb02bbaf8ef5be772b78ee24b4f.js

32 ms

event

event

5 ms

icons_data_svg.css

icons_data_svg.css

64 ms

68211.jpg

68211.jpg

234 ms

21303.jpg

21303.jpg

231 ms

357741.jpg

357741.jpg

234 ms

311476.jpg

311476.jpg

231 ms

593695.jpg

593695.jpg

150 ms

375424.jpg

375424.jpg

235 ms

186820.jpg

186820.jpg

390 ms

310231.jpg

310231.jpg

391 ms

67909.jpg

67909.jpg

390 ms

subheader_national.jpg

subheader_national.jpg

223 ms

u-WUoqrET9fUeobQW7jkRSZ2oysoEQEeKwjgmXLRnTc.ttf

u-WUoqrET9fUeobQW7jkRSZ2oysoEQEeKwjgmXLRnTc.ttf

242 ms

MTP_ySUJH_bn48VBG8sNSo3LH2FgLjViKkqswU-xtII.ttf

MTP_ySUJH_bn48VBG8sNSo3LH2FgLjViKkqswU-xtII.ttf

242 ms

omnessemibold-roman-webfont.woff

omnessemibold-roman-webfont.woff

240 ms

omnesmedium-roman-webfont.woff

omnesmedium-roman-webfont.woff

240 ms

omnesregular-roman-webfont.woff

omnesregular-roman-webfont.woff

239 ms

cheddarjack-webfont.woff

cheddarjack-webfont.woff

238 ms

loader0.js

loader0.js

144 ms

gtm.js

gtm.js

141 ms

gtm.js

gtm.js

141 ms

s-code-contents-63bc7c184d56d897ea3ca55bd6c2fc2710da1142.js

s-code-contents-63bc7c184d56d897ea3ca55bd6c2fc2710da1142.js

138 ms

icons_data_svg.css

icons_data_svg.css

106 ms

newsletter-blocker-bg.jpg

newsletter-blocker-bg.jpg

109 ms

3934-711-10-7831.js

3934-711-10-7831.js

58 ms

55.js

55.js

42 ms

standard

standard

367 ms

c

c

95 ms

ga.js

ga.js

7 ms

s05324903947766

s05324903947766

68 ms

__utm.gif

__utm.gif

22 ms

__utm.gif

__utm.gif

5 ms

Accessibility Review

thefork.be accessibility score

72

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-hidden="true"] elements contain focusable descendents

High

[aria-*] attributes do not have valid values

High

[aria-*] attributes are not valid or misspelled

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

Low

No form fields have multiple labels

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

thefork.be best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

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

thefork.be

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