3.6 sec in total
281 ms
2.5 sec
827 ms
Click here to check amazing Co Think content. Otherwise, check out these important facts you probably never knew about cothink.com
Advice and training from CoThink helps you improve your processes, solve, prevent and predict (complex) problems and ... teaches you how to do this yourself! Read more...
Visit cothink.comWe analyzed Cothink.com page load time and found that the first response time was 281 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
cothink.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value11.2 s
0/100
25%
Value7.4 s
27/100
10%
Value270 ms
81/100
30%
Value0
100/100
15%
Value8.7 s
36/100
10%
281 ms
866 ms
264 ms
346 ms
516 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 91% of them (48 requests) were addressed to the original Cothink.com, 4% (2 requests) were made to Code.jquery.com and 4% (2 requests) were made to Snap.licdn.com. The less responsive or slowest element that took the longest time to load (866 ms) belongs to the original domain Cothink.com.
Page size can be reduced by 257.8 kB (18%)
1.4 MB
1.2 MB
In fact, the total size of Cothink.com main page is 1.4 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 42.8 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. This page needs HTML code to be minified as it can gain 13.0 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 42.8 kB or 65% of the original size.
Potential reduce by 9.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. Co Think images are well optimized though.
Potential reduce by 68.7 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 68.7 kB or 78% of the original size.
Potential reduce by 136.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. Cothink.com needs all CSS files to be minified and compressed as it can save up to 136.5 kB or 70% of the original size.
Number of requests can be reduced by 17 (38%)
45
28
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Co Think. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
cothink.com
281 ms
cothink.com
866 ms
DXR.axd
264 ms
DXR.axd
346 ms
cothink.css
516 ms
js
60 ms
DXR.axd
777 ms
jquery-3.3.1.min.js
16 ms
jquery-migrate-3.0.0.min.js
18 ms
waypoint.js
286 ms
slick.min.js
377 ms
debounce.js
342 ms
main.js
363 ms
WebResource.axd
377 ms
DXR.axd
86 ms
logo.svg
103 ms
engels.svg
105 ms
duits.svg
109 ms
nederlands.svg
106 ms
btnZoeken.svg
172 ms
video.gif
782 ms
637244500153220194_Alex.jpg
199 ms
637244499805365412_Bart.jpg
198 ms
637244499386233503_Monique.jpg
200 ms
637608364933297698_ReneObbes480x.jpg
285 ms
638203653149325093_Jaap%202%20site.jpg
644 ms
637515067085599133_Stuart%20pasfoto%20(2).jpg
322 ms
637244499982323106_Henriette.jpg
321 ms
637244498694984379_Desiree.jpg
323 ms
637244498380112895_Ron.jpg
366 ms
637521017128823343_Michael%20foto%20(2).jpg
405 ms
637244500664237111_Ilse.jpg
404 ms
637244499646819559_Martijn.jpg
406 ms
637244498973337123_Jan%20Willem.jpg
431 ms
637510749018477665_Markus%201100.jpg
480 ms
637578045752295802_DDPS%20png220.JPG
478 ms
stift.png
484 ms
637238358531540108_KHF_9722_Inzpire_low.jpg
329 ms
postIT-vouw-klein.svg
288 ms
bg_pattern.jpg
290 ms
postIT-vouw.svg
295 ms
bg_form.png
381 ms
CentraleSans-Bold.woff
352 ms
icomoon.ttf
347 ms
CentraleSansRegular.woff
378 ms
TheBoldFont.woff
414 ms
Marcher-Book.woff
433 ms
Marker.woff
439 ms
cb_false_wit.png
450 ms
stiftstreep.png
423 ms
stiftstreep_horizontaal.png
466 ms
insight.min.js
39 ms
insight.old.min.js
2 ms
cothink.com accessibility score
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
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
cothink.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
cothink.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cothink.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Cothink.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.
cothink.com
Open Graph data is detected on the main page of Co Think. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: