1.4 sec in total
237 ms
999 ms
206 ms
Welcome to ww2.epeat.net homepage info - get ready to check Ww 2 EPEAT best content for United States right away, or after learning these important things about ww2.epeat.net
Visit ww2.epeat.netWe analyzed Ww2.epeat.net page load time and found that the first response time was 237 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
ww2.epeat.net performance score
237 ms
515 ms
641 ms
755 ms
499 ms
Our browser made a total of 18 requests to load all elements on the main page. We found that 50% of them (9 requests) were addressed to the original Ww2.epeat.net, 44% (8 requests) were made to Epeat.net and 6% (1 request) were made to Themes.googleusercontent.com. The less responsive or slowest element that took the longest time to load (755 ms) belongs to the original domain Ww2.epeat.net.
Page size can be reduced by 576.0 kB (72%)
799.3 kB
223.3 kB
In fact, the total size of Ww2.epeat.net main page is 799.3 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. 20% of websites need less resources to load. Javascripts take 621.0 kB which makes up the majority of the site volume.
Potential reduce by 9.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. This page needs HTML code to be minified as it can gain 1.7 kB, which is 13% 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 9.8 kB or 76% of the original size.
Potential reduce by 4.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. Ww 2 EPEAT images are well optimized though.
Potential reduce by 520.9 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 520.9 kB or 84% of the original size.
Potential reduce by 40.9 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. Ww2.epeat.net needs all CSS files to be minified and compressed as it can save up to 40.9 kB or 84% of the original size.
Number of requests can be reduced by 6 (38%)
16
10
The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ww 2 EPEAT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
ww2.epeat.net
237 ms
brewhouse.css
515 ms
jquery.js
641 ms
table.js
755 ms
table_col_reorder.js
499 ms
table_col_toggle.js
526 ms
browser.js
531 ms
prototype.js
728 ms
pagescriptsV3.js
727 ms
bg2.png
33 ms
faux-left.jpg
33 ms
logo.png
34 ms
bg-header-sm.png
42 ms
search-button.png
37 ms
social-twitter.png
35 ms
social-facebook.png
39 ms
social-vimeo.png
38 ms
mnpfi9pxYH-Go5UiibESIrO3LdcAZYWl9Si6vvxL-qU.woff
62 ms
ww2.epeat.net SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ww2.epeat.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Ww2.epeat.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.
ww2.epeat.net
Open Graph description is not detected on the main page of Ww 2 EPEAT. 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: