5.2 sec in total
849 ms
3.8 sec
555 ms
Click here to check amazing Martin Tham content. Otherwise, check out these important facts you probably never knew about martintham.com
My name is Martin Thám and I like guiding people through processes of transformation. I explore the possibilities of the body and the mind.
Visit martintham.comWe analyzed Martintham.com page load time and found that the first response time was 849 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
martintham.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value12.1 s
0/100
25%
Value15.8 s
0/100
10%
Value3,040 ms
2/100
30%
Value0
100/100
15%
Value23.7 s
1/100
10%
849 ms
247 ms
323 ms
30 ms
642 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 53% of them (29 requests) were addressed to the original Martintham.com, 13% (7 requests) were made to Youtube.com and 5% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Martintham.com.
Page size can be reduced by 171.0 kB (11%)
1.6 MB
1.4 MB
In fact, the total size of Martintham.com main page is 1.6 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 755.8 kB which makes up the majority of the site volume.
Potential reduce by 116.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 116.1 kB or 82% of the original size.
Potential reduce by 37.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. Martin Tham images are well optimized though.
Potential reduce by 8.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. This website has mostly compressed JavaScripts.
Potential reduce by 8.9 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. Martintham.com has all CSS files already compressed.
Number of requests can be reduced by 25 (52%)
48
23
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Martin Tham. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.martintham.com
849 ms
9nfux.css
247 ms
9nfux.css
323 ms
css
30 ms
64dgj.css
642 ms
64dgi.js
464 ms
9nf4a.js
345 ms
js
86 ms
index.js
227 ms
index.js
250 ms
us.core.min.js
489 ms
api.js
32 ms
wp-polyfill-inert.min.js
340 ms
regenerator-runtime.min.js
347 ms
wp-polyfill.min.js
374 ms
index.js
452 ms
info-box.min.js
459 ms
martin-tham-lgo-wim-hof.png
133 ms
slovakia-flag.png
130 ms
martin-tham-hra-na-bubny-dychacie-cvicenia-1-600x600.jpg
282 ms
martin-rohrich-1-600x600.jpg
258 ms
martin-tham-wim-hof-method-35-600x600.jpg
292 ms
chlad.png
755 ms
dychanie.png
815 ms
nastavenie-mysle.png
815 ms
dusan-plichta-wim-hof-martin-tham-1-150x150.jpg
754 ms
lucia-sudova-wim-hof-150x150.jpeg
814 ms
sdk.js
101 ms
vHKf3bXVsxA
236 ms
eX75aLSojmg
621 ms
odYUFYPKTOg
777 ms
martin-tham-wim-hof-method-instruktor.jpg
1424 ms
js
97 ms
analytics.js
122 ms
fa-brands-400.woff
709 ms
fa-regular-400.woff
1010 ms
fa-light-300.woff
1367 ms
fa-solid-900.woff
986 ms
sdk.js
22 ms
recaptcha__en.js
92 ms
collect
54 ms
collect
108 ms
www-player.css
31 ms
www-embed-player.js
64 ms
base.js
107 ms
ga-audiences
446 ms
ad_status.js
458 ms
QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js
253 ms
embed.js
206 ms
id
66 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
76 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
76 ms
Create
465 ms
Create
467 ms
Create
559 ms
martintham.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
martintham.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
martintham.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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Martintham.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 Martintham.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.
martintham.com
Open Graph data is detected on the main page of Martin Tham. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: