5.1 sec in total
203 ms
3.9 sec
927 ms
Click here to check amazing Yohann Berger content. Otherwise, check out these important facts you probably never knew about yohannberger.com
Full Stack Developer, WordPress Expert, SEO Specialist and Photographer. I build fast and responsive websites to help businesses outrank of the competition.
Visit yohannberger.comWe analyzed Yohannberger.com page load time and found that the first response time was 203 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
yohannberger.com performance score
name
value
score
weighting
Value3.1 s
48/100
10%
Value3.4 s
66/100
25%
Value6.4 s
40/100
10%
Value3,720 ms
1/100
30%
Value0.004
100/100
15%
Value15.8 s
6/100
10%
203 ms
1234 ms
63 ms
195 ms
399 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 90% of them (60 requests) were addressed to the original Yohannberger.com, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Yohannberger.com.
Page size can be reduced by 104.0 kB (12%)
859.3 kB
755.3 kB
In fact, the total size of Yohannberger.com main page is 859.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. 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 436.4 kB which makes up the majority of the site volume.
Potential reduce by 99.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 99.1 kB or 85% of the original size.
Potential reduce by 0 B
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. Yohann Berger images are well optimized though.
Potential reduce by 3.4 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 1.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. Yohannberger.com has all CSS files already compressed.
Number of requests can be reduced by 37 (82%)
45
8
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yohann Berger. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
yohannberger.com
203 ms
www.yohannberger.com
1234 ms
gtm.js
63 ms
9qc1j.css
195 ms
9qc1j.css
399 ms
post-37.css
284 ms
9qc1j.css
287 ms
post-586.css
295 ms
9qc1j.css
374 ms
post-328.css
291 ms
9qc1i.css
365 ms
9qc1j.js
459 ms
post-104.css
296 ms
post-53.css
363 ms
post-314.css
369 ms
40ew5.css
377 ms
regenerator-runtime.min.js
696 ms
wp-polyfill.min.js
695 ms
index.js
702 ms
anime.min.js
724 ms
jquery.easing.js
724 ms
uikit.min.js
724 ms
load-more.js
724 ms
main-script.js
723 ms
api.js
53 ms
index.js
723 ms
webfontloader.js
1082 ms
pr-main.js
1088 ms
isotope.js
1087 ms
webpack.runtime.min.js
1087 ms
frontend-modules.min.js
1087 ms
waypoints.min.js
1087 ms
core.min.js
1578 ms
swiper.min.js
1578 ms
share-link.min.js
1578 ms
dialog.min.js
1577 ms
frontend.min.js
1578 ms
preloaded-modules.min.js
1578 ms
js
60 ms
poppins-normal-700.woff
1035 ms
poppins-normal-800.woff
921 ms
poppins-normal-900.woff
920 ms
poppins-normal-600.woff
1036 ms
poppins-normal-500.woff
1036 ms
poppins-normal-400.woff
1034 ms
poppins-normal-300.woff
1035 ms
poppins-normal-200.woff
1036 ms
poppins-normal-100.woff
1442 ms
fontawesome-webfont.woff
1436 ms
roboto-normal-300.woff
1435 ms
roboto-normal-100.woff
1035 ms
roboto-normal-400.woff
1435 ms
roboto-normal-500.woff
1036 ms
roboto-normal-700.woff
1434 ms
roboto-normal-900.woff
1435 ms
iconfont.ttf
1438 ms
fa-brands-400.woff
1439 ms
bricks.jpg
1429 ms
recaptcha__en.js
662 ms
css
497 ms
pyramid.jpg
1065 ms
mirror.jpg
1066 ms
diagonal.jpg
1007 ms
stairs.jpg
1008 ms
clouds.jpg
1008 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpfBJ.ttf
27 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyovBJ.ttf
77 ms
yohannberger.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
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
Links do not have a discernible name
yohannberger.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
yohannberger.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Yohannberger.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 Yohannberger.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.
yohannberger.com
Open Graph data is detected on the main page of Yohann Berger. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: