3.3 sec in total
714 ms
2.3 sec
327 ms
Visit johnhine.com now to see the best up-to-date Johnhine content for United States and also check out these interesting facts you probably never knew about johnhine.com
We've got over 60 years of dealership experience that allows us to stand out from many other car dealers in Temecula. For excellent service and a fine selection of cars, visit the team at Hello M...
Visit johnhine.comWe analyzed Johnhine.com page load time and found that the first response time was 714 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
johnhine.com performance score
714 ms
71 ms
111 ms
97 ms
69 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 8% of them (8 requests) were addressed to the original Johnhine.com, 42% (40 requests) were made to Static.dealer.com and 14% (13 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (714 ms) belongs to the original domain Johnhine.com.
Page size can be reduced by 1.1 MB (41%)
2.7 MB
1.6 MB
In fact, the total size of Johnhine.com main page is 2.7 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 101.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. 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 101.8 kB or 79% of the original size.
Potential reduce by 11.0 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. Johnhine images are well optimized though.
Potential reduce by 412.0 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 412.0 kB or 68% of the original size.
Potential reduce by 574.2 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. Johnhine.com needs all CSS files to be minified and compressed as it can save up to 574.2 kB or 87% of the original size.
Number of requests can be reduced by 53 (58%)
91
38
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Johnhine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.johnhine.com
714 ms
font-face-default.css
71 ms
blue_white.css
111 ms
blue_white-widgets.css
97 ms
widget.css
69 ms
widget.css
62 ms
custom.css
143 ms
newrelic.js
67 ms
modernizr-2.6.2.min.js
91 ms
pxa.min.js
16 ms
pixall.min.js
15 ms
blue_white-blessed1.css
73 ms
iframe.php
137 ms
cookie-messaging.html
68 ms
2016_46.png
61 ms
d9a2df09f78542dab855b1f14d1323abx.jpg
257 ms
e524a1ec9d5adb85a36ecfdcbc1a1e98x.jpg
263 ms
909c205803d5436408dab0fd0edde1e4x.jpg
223 ms
bce28d85c6cfff951d12c95dd880a19cx.jpg
261 ms
2016_26.png
56 ms
2016_46.png
55 ms
2016_54.png
56 ms
9332_26.png
55 ms
183x125.png
58 ms
blank.gif
58 ms
webfont.ttf
149 ms
webfont.ttf
63 ms
webfont.ttf
71 ms
webfont.ttf
115 ms
conversion.js
23 ms
ddc.jquery.min.js
107 ms
ddc.min.js
74 ms
jquery.backstretch.min.js
105 ms
widget.min.js
105 ms
widget.min.js
106 ms
widget.min.js
145 ms
dropdown.min.js
168 ms
widget.min.js
211 ms
widget.min.js
168 ms
jquery.timeago.min.js
170 ms
widget.min.js
169 ms
tracker.min.js
169 ms
widget.min.js
209 ms
widget.min.js
383 ms
widget.min.js
210 ms
data-layer-helper.min.js
276 ms
variation.min.js
324 ms
ddc-logo-black.png
235 ms
font.woff
252 ms
analytics.js
52 ms
121 ms
gtm.js
80 ms
pixel
157 ms
105 ms
pixel
22 ms
pixel
50 ms
pixel.php
50 ms
pixel.php
81 ms
fbdrop.php
45 ms
profiles
242 ms
collect
218 ms
0d72fe5ac2969fc549b1a4b08de5207ax.jpg
327 ms
7aa37f60f4ac89362016f6bd198d2c1ex.jpg
413 ms
f7ff8f64a9fc92181b816a57e500349fx.jpg
408 ms
e47ff10133802726f1a2de1a8c626de9x.jpg
392 ms
f63bff96819b8645fccbf7409d96a724x.jpg
397 ms
745d94dedb097bd50162765c48804c59x.jpg
359 ms
96e3ed74f5436a894451b5a46bf4d4fex.jpg
668 ms
collect
175 ms
collect
177 ms
collect
177 ms
mycars-icon-sprite-white.png
231 ms
clear.gif
203 ms
bbb.png
162 ms
goldCup2.png
162 ms
header-logo.png
208 ms
ui.min.js
113 ms
dialog.min.js
117 ms
collect
65 ms
collect
63 ms
collect
63 ms
collect
65 ms
validator.min.js
62 ms
jquery.unveil.min.js
62 ms
jcarousel.min.js
32 ms
users
322 ms
blue_white-blessed1.css
95 ms
entry.htm
158 ms
3959d7dac307f3cdde464efa7b90d0a5x.jpg
13 ms
collect
9 ms
collect
7 ms
collect
6 ms
collect
7 ms
nr-632.min.js
17 ms
vms.js
91 ms
82e1cf9367
46 ms
johnhine.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnhine.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 Johnhine.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.
johnhine.com
Open Graph description is not detected on the main page of Johnhine. 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: