Tools & Wizards About Us
thinc.be screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

thinc.be

Ben Eelen - User Experience & Web Design Consultant

Page Load Speed

1.9 sec in total

First Response

336 ms

Resources Loaded

1.4 sec

Page Rendered

189 ms

thinc.be screenshot

About Website

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

Are you looking to increase your business value? I can help you, creating a better user experience throughout your digital products.

Visit thinc.be

Key Findings

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

Performance Metrics

thinc.be performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

62/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

thinc.be

336 ms

thinc.be

67 ms

vjx2vsr.css

84 ms

autoptimize_e8ac5939d81f454eb04dc4947b88502d.css

48 ms

lazysizes.min.js

57 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 55% of them (11 requests) were addressed to the original Thinc.be, 40% (8 requests) were made to Use.typekit.net and 5% (1 request) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (741 ms) belongs to the original domain Thinc.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.0 kB (4%)

Content Size

614.3 kB

After Optimization

588.2 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Thinc.be main page is 614.3 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. 40% of websites need less resources to load. Images take 580.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 26.0 kB

  • Original 34.0 kB
  • After minification 33.8 kB
  • After compression 7.9 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 26.0 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 580.3 kB
  • After minification 580.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. Thinc images are well optimized though.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 4 (40%)

Requests Now

10

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thinc.be

thinc.be

336 ms

thinc.be

thinc.be

67 ms

vjx2vsr.css

vjx2vsr.css

84 ms

autoptimize_e8ac5939d81f454eb04dc4947b88502d.css

autoptimize_e8ac5939d81f454eb04dc4947b88502d.css

48 ms

lazysizes.min.js

lazysizes.min.js

57 ms

jquery.min.js

jquery.min.js

54 ms

vendor.min.js

vendor.min.js

60 ms

main.min.js

main.min.js

55 ms

p.css

p.css

22 ms

matomo.js

matomo.js

124 ms

d

d

22 ms

d

d

23 ms

d

d

35 ms

d

d

35 ms

d

d

35 ms

d

d

35 ms

d

d

46 ms

betterworks.woff

betterworks.woff

228 ms

matomo.php

matomo.php

741 ms

BLD_6106-Kopie1-scaled-1.jpg

BLD_6106-Kopie1-scaled-1.jpg

260 ms

Accessibility Review

thinc.be accessibility score

58

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

SEO Factors

thinc.be SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

thinc.be

Open Graph data is detected on the main page of Thinc. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: