1.8 sec in total
145 ms
1.4 sec
279 ms
Visit now.ehow.com now to see the best up-to-date Now EHow content for United States and also check out these interesting facts you probably never knew about now.ehow.com
Ask questions, find answers, and discuss ideas with eHow's helpful Community.
Visit now.ehow.comWe analyzed Now.ehow.com page load time and found that the first response time was 145 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
now.ehow.com performance score
145 ms
642 ms
67 ms
66 ms
68 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Now.ehow.com, 58% (25 requests) were made to Static.ehownowcdn.com and 5% (2 requests) were made to Images02.ehowcdn.com. The less responsive or slowest element that took the longest time to load (642 ms) relates to the external source Ehow.com.
Page size can be reduced by 1.2 MB (57%)
2.1 MB
918.3 kB
In fact, the total size of Now.ehow.com main page is 2.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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 258.9 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 258.9 kB or 63% of the original size.
Potential reduce by 9.5 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. Now EHow images are well optimized though.
Potential reduce by 773.7 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 773.7 kB or 67% of the original size.
Potential reduce by 161.3 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. Now.ehow.com needs all CSS files to be minified and compressed as it can save up to 161.3 kB or 54% of the original size.
Number of requests can be reduced by 17 (49%)
35
18
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Now EHow. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
now.ehow.com
145 ms
community
642 ms
community-on-community-d81962d0.css
67 ms
community-on-community-81200c22.less.css
66 ms
community-common-bdb85e07.less.css
68 ms
community-on-community-desktop-99c7a56b.css
82 ms
community-on-community-desktop-6110ba48.less.css
74 ms
community-on-community-thread-5df0f8a0.less.css
71 ms
community-leaderboard-dae6e1e4.less.css
75 ms
ehow-base-1a39d744.js
74 ms
mixpanel-b6043d5e.js
74 ms
community-on-community-df8b7f13.js
76 ms
community-common-e68bc5bf.js
75 ms
community-on-community-desktop-93284033.js
73 ms
community-on-community-thread-afab0264.js
74 ms
auth.js
22 ms
9718688.js
241 ms
mixpanel-2.2.min.js
109 ms
gtm.js
117 ms
photo.jpg
136 ms
8e4ce706103bb7ef6f064bd1b2ec8405.jpg
411 ms
logov3.png
63 ms
diyhome.png
64 ms
cooking-entertaining.png
64 ms
bofa_smartliving.png
63 ms
avatar-user-default-small-dark.png
62 ms
chris-deziel.png
63 ms
layout.png
73 ms
e5ffd96f0381b2b976ad1406a35ea938.jpg
468 ms
492Ht3J4TkpfgGCMD8L
38 ms
APvEP9M=
38 ms
eleganticons.woff
70 ms
analytics.js
120 ms
museosans_300.woff
83 ms
levserif-handcut-webfont.woff
82 ms
ehowcom.woff
82 ms
geo2.js
144 ms
event
103 ms
icon1.png
206 ms
91 ms
collect
18 ms
collect
74 ms
event
11 ms
now.ehow.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Now.ehow.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 Now.ehow.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.
now.ehow.com
Open Graph description is not detected on the main page of Now EHow. 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: