3.2 sec in total
78 ms
2.1 sec
1 sec
Click here to check amazing Johnlutz content. Otherwise, check out these important facts you probably never knew about johnlutz.com
Nutrition, natural healthcare, research, consulting. Immune support research summary, over 1500 studies cited. 2000 Bible verses by topic. Biblical healthcare.
Visit johnlutz.comWe analyzed Johnlutz.com page load time and found that the first response time was 78 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
johnlutz.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value2.9 s
81/100
25%
Value7.2 s
30/100
10%
Value6,210 ms
0/100
30%
Value0
100/100
15%
Value16.4 s
5/100
10%
78 ms
623 ms
38 ms
40 ms
721 ms
Our browser made a total of 22 requests to load all elements on the main page. We found that 27% of them (6 requests) were addressed to the original Johnlutz.com, 45% (10 requests) were made to Youtube.com and 9% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (842 ms) relates to the external source Static.doubleclick.net.
Page size can be reduced by 107.6 kB (29%)
366.9 kB
259.3 kB
In fact, the total size of Johnlutz.com main page is 366.9 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. 80% 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 158.2 kB which makes up the majority of the site volume.
Potential reduce by 102.6 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 14.4 kB, which is 11% 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 102.6 kB or 76% of the original size.
Potential reduce by 341 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. Johnlutz images are well optimized though.
Potential reduce by 2.5 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 2.1 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. Johnlutz.com has all CSS files already compressed.
Number of requests can be reduced by 8 (42%)
19
11
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Johnlutz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
johnlutz.com
78 ms
johnlutz.com
623 ms
font-awesome.min.css
38 ms
19-11-09.css
40 ms
videoseries
721 ms
favicon16x40.jpg
55 ms
DzENjs1CctI
133 ms
KIcWskZUS3A
643 ms
wq29rADk9Os
212 ms
gKUyKscsgeY
552 ms
miBjRpX60t8
131 ms
myFunction.js
38 ms
print.css
21 ms
www-player.css
6 ms
www-embed-player.js
29 ms
base.js
84 ms
ad_status.js
842 ms
6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js
477 ms
embed.js
80 ms
id
346 ms
AIdro_lshbwuUC6f3nDmX0N-TdbslKi-xZQIoC1AEJDu=s68-c-k-c0x00ffffff-no-rj
166 ms
fontawesome-webfont.woff
158 ms
johnlutz.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.
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
<frame> or <iframe> elements do not have a title
johnlutz.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Page has valid source maps
johnlutz.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Johnlutz.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 Johnlutz.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.
johnlutz.com
Open Graph description is not detected on the main page of Johnlutz. 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: