Tools & Wizards About Us
thinqbetter.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

thinqbetter.com

THINK BETTER - THINK QUALITY | Regulatory Consulting for the medical device industry.

Page Load Speed

4.2 sec in total

First Response

355 ms

Resources Loaded

2.9 sec

Page Rendered

927 ms

thinqbetter.com screenshot

About Website

Click here to check amazing Thinq BETTER content. Otherwise, check out these important facts you probably never knew about thinqbetter.com

Regulatory conulting for medical devices and IVDs - Clinical evaluations, quality management, risk management and more.

Visit thinqbetter.com

Key Findings

We analyzed Thinqbetter.com page load time and found that the first response time was 355 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

thinqbetter.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.109

87/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

thinqbetter.com

355 ms

thinqbetter.com

458 ms

www.thinqbetter.com

573 ms

get_css.php

222 ms

google-font-open-sans_local.css

331 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 68% of them (19 requests) were addressed to the original Thinqbetter.com, 11% (3 requests) were made to App.usercentrics.eu and 4% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Thinqbetter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 251.3 kB (17%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thinqbetter.com main page is 1.5 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. 70% of websites need less resources to load. Images take 591.0 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 248.4 kB

  • Original 285.4 kB
  • After minification 263.5 kB
  • After compression 37.1 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 248.4 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 591.0 kB
  • After minification 589.7 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. Thinq BETTER images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 527.1 kB
  • After minification 527.1 kB
  • After compression 525.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 506 B

  • Original 52.0 kB
  • After minification 52.0 kB
  • After compression 51.5 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. Thinqbetter.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

24

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thinq BETTER. 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

thinqbetter.com

thinqbetter.com

355 ms

thinqbetter.com

thinqbetter.com

458 ms

www.thinqbetter.com

www.thinqbetter.com

573 ms

get_css.php

get_css.php

222 ms

google-font-open-sans_local.css

google-font-open-sans_local.css

331 ms

main.js

main.js

31 ms

api.js

api.js

47 ms

totaljs.js

totaljs.js

555 ms

bundle.js

bundle.js

73 ms

recaptcha__en.js

recaptcha__en.js

139 ms

thinqbetter_frei3

thinqbetter_frei3

178 ms

compass_w1200.jpg

compass_w1200.jpg

271 ms

values_check_icon.png

values_check_icon.png

290 ms

about_DSC_0305-2L.jpg

about_DSC_0305-2L.jpg

309 ms

about_icon_expertise.png

about_icon_expertise.png

382 ms

thanks.jpg

thanks.jpg

1168 ms

choose_icon_environment.png

choose_icon_environment.png

397 ms

choose_icon_partner.png

choose_icon_partner.png

398 ms

choose_icon_smile.png

choose_icon_smile.png

398 ms

pms-blog.jpg

pms-blog.jpg

415 ms

rollator-blog.jpg

rollator-blog.jpg

512 ms

fda-zulassung-medizinprodukte-og.jpg

fda-zulassung-medizinprodukte-og.jpg

747 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

573 ms

1px.png

1px.png

7 ms

en.json

en.json

171 ms

en

en

142 ms

erecht24_logo_white.png

erecht24_logo_white.png

432 ms

graphql

graphql

137 ms

Accessibility Review

thinqbetter.com accessibility score

87

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

thinqbetter.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Missing source maps for large first-party JavaScript

SEO Factors

thinqbetter.com SEO score

93

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

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 Thinqbetter.com 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 Thinqbetter.com 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

thinqbetter.com

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