4.5 sec in total
1.1 sec
3 sec
412 ms
Visit johnholliday.net now to see the best up-to-date John Holliday content and also check out these interesting facts you probably never knew about johnholliday.net
Visit johnholliday.netWe analyzed Johnholliday.net page load time and found that the first response time was 1.1 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
johnholliday.net performance score
1100 ms
55 ms
89 ms
92 ms
97 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 92% of them (72 requests) were addressed to the original Johnholliday.net, 6% (5 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Johnholliday.net.
Page size can be reduced by 1.4 MB (74%)
1.9 MB
488.7 kB
In fact, the total size of Johnholliday.net main page is 1.9 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. 65% of websites need less resources to load. Javascripts take 885.5 kB which makes up the majority of the site volume.
Potential reduce by 50.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. 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 50.6 kB or 80% of the original size.
Potential reduce by 128.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. Obviously, John Holliday needs image optimization as it can save up to 128.3 kB or 47% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 642.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 642.5 kB or 73% of the original size.
Potential reduce by 605.0 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. Johnholliday.net needs all CSS files to be minified and compressed as it can save up to 605.0 kB or 87% of the original size.
Number of requests can be reduced by 60 (81%)
74
14
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John Holliday. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
johnholliday.net
1100 ms
wp-emoji-release.min.js
55 ms
ie.css
89 ms
styles.css
92 ms
cool-tag-cloud.css
97 ms
layerslider.css
102 ms
css
25 ms
swipebox.min.css
103 ms
settings.css
91 ms
woocommerce-layout.css
131 ms
woocommerce.css
134 ms
twitter-feed.css
129 ms
pagenavi-css.css
145 ms
css
45 ms
style.css
145 ms
css
43 ms
eventon_styles.css
145 ms
font-awesome.css
161 ms
shortcodes.css
164 ms
tx_styles.css
171 ms
fc_styles.css
179 ms
shortcodes_responsive.css
172 ms
magnific_popup.css
179 ms
wpgmza_style.css
196 ms
jquery.js
232 ms
jquery-migrate.min.js
198 ms
layerslider.kreaturamedia.jquery.js
235 ms
greensock.js
235 ms
layerslider.transitions.js
202 ms
jquery.swipebox.min.js
230 ms
front.js
234 ms
jquery.themepunch.tools.min.js
277 ms
jquery.themepunch.revolution.min.js
268 ms
css
36 ms
css
35 ms
font-awesome.css
265 ms
eventon_dynamic_styles.css
269 ms
frontend-builder-global-functions.js
277 ms
jquery.form.min.js
273 ms
scripts.js
304 ms
add-to-cart.min.js
303 ms
js
108 ms
jquery.blockUI.min.js
307 ms
woocommerce.min.js
280 ms
jquery.cookie.min.js
247 ms
cart-fragments.min.js
245 ms
tx_wc_variable.js
263 ms
tx_script.js
262 ms
custom.js
266 ms
jquery.fitvids.js
279 ms
waypoints.min.js
254 ms
jquery.magnific-popup.js
278 ms
frontend-builder-scripts.js
281 ms
style.css
288 ms
lgs_jquery.cycle2.js
259 ms
wp-embed.min.js
259 ms
eventon_functions.js
242 ms
jquery.mobile.min.js
241 ms
eventon_script.js
637 ms
eventon_gen_maps.js
632 ms
se_evo_script.js
629 ms
eventon_init_gmap.js
629 ms
Logo-400x30.png
123 ms
hero-maximize-roi.jpg
113 ms
hero-content-modeling.jpg
117 ms
hero-user-engagement.jpg
197 ms
INFO-RM1.png
205 ms
ETmodules_v2_4.ttf
89 ms
evo_fontawesome-webfont.woff
195 ms
revolution.extension.slideanims.min.js
54 ms
revolution.extension.actions.min.js
54 ms
revolution.extension.layeranimation.min.js
57 ms
revolution.extension.kenburn.min.js
58 ms
revolution.extension.navigation.min.js
57 ms
revolution.extension.parallax.min.js
61 ms
johnholliday.net
695 ms
fontawesome-webfont.woff
147 ms
woocommerce-smallscreen.css
38 ms
johnholliday.net SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnholliday.net 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 Johnholliday.net 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.
johnholliday.net
Open Graph description is not detected on the main page of John Holliday. 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: