6.3 sec in total
247 ms
2.7 sec
3.4 sec
Welcome to ewillys.com homepage info - get ready to check EWillys best content for United States right away, or after learning these important things about ewillys.com
Visit ewillys.comWe analyzed Ewillys.com page load time and found that the first response time was 247 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ewillys.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value6.5 s
9/100
25%
Value11.6 s
4/100
10%
Value2,430 ms
5/100
30%
Value0
100/100
15%
Value58.3 s
0/100
10%
247 ms
48 ms
62 ms
63 ms
44 ms
Our browser made a total of 257 requests to load all elements on the main page. We found that 50% of them (128 requests) were addressed to the original Ewillys.com, 11% (27 requests) were made to Facebook.com and 4% (10 requests) were made to Thumbs1.ebaystatic.com. The less responsive or slowest element that took the longest time to load (614 ms) relates to the external source Adn.ebay.com.
Page size can be reduced by 2.0 MB (20%)
10.1 MB
8.2 MB
In fact, the total size of Ewillys.com main page is 10.1 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. 85% 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. Images take 7.8 MB which makes up the majority of the site volume.
Potential reduce by 321.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 321.1 kB or 87% of the original size.
Potential reduce by 370.2 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. EWillys images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 63% of the original size.
Potential reduce by 180.6 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. Ewillys.com needs all CSS files to be minified and compressed as it can save up to 180.6 kB or 68% of the original size.
Number of requests can be reduced by 88 (36%)
247
159
The browser has sent 247 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EWillys. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.ewillys.com
247 ms
wp-emoji-release.min.js
48 ms
wpfp.css
62 ms
wpabi.css
63 ms
css
44 ms
dashicons.min.css
94 ms
admin-bar.min.css
66 ms
front_end_style.css
68 ms
desktop_style.css
77 ms
styles.css
92 ms
style.css
92 ms
jss-style.css
97 ms
style.css
97 ms
pagenavi-css.css
106 ms
css
26 ms
style.css
123 ms
jquery.js
158 ms
jquery-migrate.min.js
125 ms
wpabi.js
127 ms
script.js
128 ms
wpfp.js
136 ms
adsbygoogle.js
14 ms
jquery-1.6.2-min.js
614 ms
ebay_activeContent-min.js
512 ms
admin-bar.min.js
140 ms
jquery.form.min.js
141 ms
scripts.js
206 ms
jss-script.min.js
206 ms
navigation.js
207 ms
wp-embed.min.js
209 ms
all.js
51 ms
1
381 ms
btn_donateCC_LG.gif
204 ms
bkg-body.png
108 ms
header-top.png
107 ms
logo.png
107 ms
home_16x16.png
107 ms
about_16x16.png
107 ms
mail_24x24.png
107 ms
biscuit-lores.jpg
144 ms
sub_arrow.gif
338 ms
buysellhelp_16x16.png
145 ms
jeeps_16x16.png
144 ms
features_16x16.png
144 ms
ideas_16x16.png
143 ms
forums_16x16.png
158 ms
parts_16x16.png
159 ms
delete_o_16x16.png
160 ms
alaska-or-rust-web-ad-ewillys6-2.jpg
159 ms
up_arrow_16x16.png
159 ms
bubble.png
192 ms
1941-10-15-craig-empire-courier-colorado-Ford-GP-451x650.jpg
212 ms
forum_options.png
191 ms
star.png
190 ms
loading.gif
191 ms
dibujo_mapa_texas_jeep_cj2a_texto_t%C3%ADtulo_lema_1_copia_web.jpeg
251 ms
1964-cj3b-lakewood-colo1.jpg
257 ms
1964-cj3b-lakewood-colo2.jpg
221 ms
1964-cj3b-lakewood-colo3.jpg
281 ms
1964-cj3b-lakewood-colo4.jpg
244 ms
1951-cj3a-sfbay-cali2.jpg
257 ms
1951-cj3a-sfbay-cali3.jpg
275 ms
1951-cj3a-sfbay-cali4.jpg
281 ms
1955-cj3b-montrose-colo2.jpg
282 ms
pixel.gif
203 ms
ca-pub-4090537347449382.js
97 ms
zrt_lookup.html
133 ms
show_ads_impl.js
105 ms
1955-cj3b-montrose-colo3.jpg
269 ms
1955-cj3b-montrose-colo4.jpg
289 ms
1953-cj3b-potlatch-id1.jpg
294 ms
1953-cj3b-potlatch-id2.jpg
295 ms
1953-cj3b-potlatch-id3.jpg
278 ms
1953-cj3b-potlatch-id4.jpg
213 ms
1948-cj2a-troy-co11.jpg
240 ms
1948-cj2a-troy-co12.jpg
244 ms
1948-cj2a-troy-co13.jpg
244 ms
1947-cj2a-santarosa-calif1.jpg
246 ms
1947-cj2a-santarosa-calif2.jpg
246 ms
65 ms
ads
196 ms
osd.js
34 ms
1947-cj2a-santarosa-calif3.jpg
229 ms
1947-cj2a-santarosa-calif4.jpg
232 ms
1951-m38-phx-ariz1.jpg
242 ms
1951-m38-phx-ariz2.jpg
237 ms
1951-m38-phx-ariz9.jpg
238 ms
0sTQzbapM8j.js
29 ms
0sTQzbapM8j.js
53 ms
ads
202 ms
1946-cj2a-chicka-ga1.jpg
223 ms
1946-cj2a-chicka-ga2.jpg
252 ms
1946-cj2a-chicka-ga3.jpg
253 ms
1946-cj2a-chicka-ga4.jpg
261 ms
1950-jeepster-lompoc-cali4.jpg
263 ms
ads
171 ms
1950-jeepster-lompoc-cali3.jpg
232 ms
1950-jeepster-lompoc-cali2.jpg
233 ms
1950-jeepster-lompoc-cali1.jpg
258 ms
year-cj3a-lacali.jpg
254 ms
year-cj3a-lacali2.jpg
244 ms
1943-mb-sd-cali.jpg
233 ms
generator-engine-ca.jpg
211 ms
1947-cj2a-phx-ariz91.jpg
204 ms
1947-cj2a-phx-ariz92.jpg
229 ms
1947-cj2a-phx-ariz93.jpg
228 ms
1947-cj2a-phx-ariz94.jpg
220 ms
1957-cj5-eaglecreek-or1.jpg
215 ms
1957-cj5-eaglecreek-or4.jpg
214 ms
1957-cj5-eaglecreek-or2.jpg
214 ms
1957-cj5-eaglecreek-or3.jpg
245 ms
1948-02-mechanix-illustrated-516x650.jpg
223 ms
1942-04-21-scout-car-onto-plane1-552x650.jpg
236 ms
1942-04-21-scout-car-onto-plane2-538x650.jpg
235 ms
1948-cj2a-yubacity-cali36.jpg
232 ms
1948-cj2a-yubacity-cali37.jpg
232 ms
adServer.bs
218 ms
skeleton.js
76 ms
m_window_focus_non_hydra.js
31 ms
osd_listener.js
35 ms
m_qs_click_protection.js
38 ms
abg.js
40 ms
1948-cj2a-yubacity-cali38.jpg
218 ms
gen_204
14 ms
ad
43 ms
o16FtOAn.js
37 ms
1948-cj2a-yubacity-cali39.jpg
210 ms
1946-cj2-poplarbluff-mo0.jpg
249 ms
1946-cj2-poplarbluff-mo1.jpg
248 ms
1946-cj2-poplarbluff-mo3.jpg
246 ms
1946-cj2-poplarbluff-mo4.jpg
245 ms
1946-cj2a-qc-ia1.jpg
225 ms
1946-cj2a-qc-ia2.jpg
223 ms
1946-cj2a-qc-ia3.jpg
254 ms
1946-cj2a-qc-ia4.jpg
253 ms
2014-03-11-kaiser-willys-ad.jpg
253 ms
2014-peter-debella-jeep-parts2.jpg
251 ms
abg.js
2 ms
lidar.js
23 ms
d5qAyLYU.js
22 ms
pixel
27 ms
a_tn_aol.js
92 ms
ww2-jeeps-ad-hinton.jpg
224 ms
transparent.png
31 ms
2016-ron-fitzpatrick-ad.gif
214 ms
pixel
67 ms
2016-army-jeep-parts-george-baxter-ad.jpg
247 ms
pixel
66 ms
ebay_ad.png
246 ms
calendar-ad-2018-300px.jpg
264 ms
2016-dispather-magazine-ad.jpg
240 ms
9im3l02I.html
19 ms
cb
515 ms
bullet-orange.gif
237 ms
old-carbs-ad.jpg
218 ms
facebook_button_ad.png
240 ms
kaiser-willys-free-catalogue.jpg
239 ms
2017-02-18-allied-ad.jpg
243 ms
T8Ys39_ecZUP0z5o0qwgiftCx6c5Z_CDv350QIo51NY.js
7 ms
2013-southwest-tour-ad.jpg
247 ms
2013-eastcoast-tour-ad.jpg
221 ms
2014-southwest-westcoast-trip.jpg
214 ms
2015-texas-trip.jpg
229 ms
2016-mountainwest-trip.jpg
228 ms
2016-fall-ut-nm-tx-la.jpg
234 ms
2015-03-18-willys-america-logo4.jpg
245 ms
polyfills.promise.js
71 ms
polyfills.intersection-observer.js
84 ms
stormtrooper.css
106 ms
beacon
111 ms
Jeep_728x90.jpg
141 ms
sync
81 ms
dt
109 ms
vast.js
60 ms
jwpsrv.js
71 ms
related.js
71 ms
jwplayer.controls.js
70 ms
skeleton.js
41 ms
p2
5 ms
140.jpg
106 ms
140.jpg
102 ms
140.jpg
99 ms
140.jpg
98 ms
140.jpg
54 ms
140.jpg
55 ms
140.jpg
57 ms
140.jpg
68 ms
140.jpg
55 ms
140.jpg
59 ms
140.jpg
58 ms
140.jpg
57 ms
140.jpg
59 ms
140.jpg
55 ms
140.jpg
56 ms
140.jpg
58 ms
140.jpg
59 ms
140.jpg
66 ms
140.jpg
66 ms
140.jpg
58 ms
140.jpg
59 ms
140.jpg
63 ms
140.jpg
60 ms
140.jpg
60 ms
140.jpg
60 ms
140.jpg
62 ms
140.jpg
76 ms
140.jpg
60 ms
140.jpg
59 ms
imagelink_sprite.png
379 ms
platform.js
243 ms
arrow.png
39 ms
ga.js
4 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
187 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
302 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
317 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
409 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
202 ms
AAABVuGyrgAA
101 ms
__utm.gif
199 ms
like.php
390 ms
like.php
399 ms
like.php
385 ms
like.php
394 ms
like.php
304 ms
like.php
304 ms
like.php
406 ms
like.php
406 ms
like.php
411 ms
like.php
417 ms
like.php
424 ms
like.php
420 ms
like.php
436 ms
like.php
435 ms
like.php
427 ms
like.php
455 ms
like.php
439 ms
like.php
442 ms
like.php
458 ms
like.php
450 ms
like.php
445 ms
like.php
527 ms
like.php
515 ms
like.php
523 ms
like.php
522 ms
like.php
458 ms
1x1_for_Impressions.gif
291 ms
cb=gapi.loaded_0
29 ms
cb=gapi.loaded_1
119 ms
fastbutton
224 ms
0sTQzbapM8j.js
96 ms
4qFiRLLPSF7.js
279 ms
lH1ibRl5GKq.png
291 ms
rs=AGLTcCOUSJIRFuWfIxRmYNF0NPW_T9054A
131 ms
postmessageRelay
131 ms
971028622-postmessagerelay.js
32 ms
rpc:shindig_random.js
28 ms
cb=gapi.loaded_0
3 ms
ewillys.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ewillys.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
ewillys.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ewillys.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ewillys.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.
ewillys.com
Open Graph description is not detected on the main page of EWillys. 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: