4.5 sec in total
1.1 sec
2.5 sec
946 ms
Click here to check amazing Wetherburnehomes content. Otherwise, check out these important facts you probably never knew about wetherburnehomes.com
Builder of Custom Homes in Vienna, Virginia
Visit wetherburnehomes.comWe analyzed Wetherburnehomes.com 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.
wetherburnehomes.com performance score
1144 ms
73 ms
128 ms
201 ms
144 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 89% of them (67 requests) were addressed to the original Wetherburnehomes.com, 5% (4 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Wetherburnehomes.com.
Page size can be reduced by 120.6 kB (5%)
2.2 MB
2.1 MB
In fact, the total size of Wetherburnehomes.com main page is 2.2 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. 75% 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 24.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 24.1 kB or 78% of the original size.
Potential reduce by 957 B
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. Wetherburnehomes images are well optimized though.
Potential reduce by 69.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 69.7 kB or 60% of the original size.
Potential reduce by 25.8 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. Wetherburnehomes.com needs all CSS files to be minified and compressed as it can save up to 25.8 kB or 83% of the original size.
Number of requests can be reduced by 22 (30%)
74
52
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wetherburnehomes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
wetherburnehomes.com
1144 ms
reset.css
73 ms
screen.css
128 ms
jquery-1.4.2.min.js
201 ms
global.js
144 ms
easySlider1.7.js
147 ms
slideshow.css
184 ms
jquery.easing.js
198 ms
script.js
197 ms
ga.js
157 ms
900_9_800_300.jpg
558 ms
bg_body.gif
116 ms
bg_nav_main.jpg
115 ms
logo.jpg
115 ms
bg_transparent.png
114 ms
bg_block-static.jpg
105 ms
bg_content_main.gif
114 ms
2012greenhomebuilder.jpg
332 ms
bg_boards.jpg
222 ms
badge_sold.jpg
221 ms
icn_energystar.jpg
221 ms
icn_twitter.png
221 ms
icn_facebook.png
212 ms
icn_linkedin.png
327 ms
icn_rss.png
381 ms
cominghome.jpg
667 ms
Vale800300.jpg
377 ms
401OK2_800_300.jpg
532 ms
jamestown_OTB.jpg
544 ms
115_Kingsley_800_f.jpg
514 ms
900_9_110_65_frt.jpg
378 ms
cominghome-thumb.jpg
530 ms
115_Kingsley_kit_110.jpg
531 ms
401OK_110.jpg
530 ms
Jamestown_110.jpg
537 ms
203_Mashie_110.jpg
539 ms
528_N_frtA_525245_.jpg
542 ms
10016_C_525245_3D.jpg
542 ms
517_N_frt_545245.jpg
541 ms
900___545245_haig.jpg
540 ms
131_K_frt_545245.jpg
654 ms
Sprangle_frt_525245.jpg
611 ms
405_M_525245_frt.jpg
652 ms
900_P_545245_c1.jpg
609 ms
10016_C_rear_525245_3D.jpg
607 ms
307_M_525245_frt_652014.jpg
714 ms
118_Glyndon_3D+525245.jpg
847 ms
900_P_kit_otb_525245.jpg
709 ms
353_Park_front_545245.jpg
712 ms
Plan_L_e2_525_245.jpg
712 ms
400_M_fiish_545245.jpg
709 ms
10517V_ext_525245.jpg
849 ms
Plan_L_Nocar_525245.jpg
849 ms
Murray_otb_front.jpg
878 ms
401_Oak_Knoll_525245.jpg
845 ms
220_Cherry_525_A.jpg
846 ms
1301_K_frt_525245.jpg
848 ms
Plan_L_1c_545_245.jpg
876 ms
TVienna_GREEN_HOME_2015.jpg
876 ms
131_K_frt_530320_rev11.jpg
976 ms
widgets.js
104 ms
__utm.gif
22 ms
icn_home.gif
174 ms
528_N_530320_482016.jpg
618 ms
bg_followus.jpg
164 ms
widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html
214 ms
icn_arrow_left.jpg
109 ms
icn_arrow_right.jpg
151 ms
bg_block-active.jpg
107 ms
517_N_530320_const.jpg
483 ms
ph_buildonyourlot.jpg
502 ms
settings
291 ms
moment~timeline~tweet.ae149926685a43cb146e35371430188e.js
18 ms
timeline.687eed636a16648c9f0b1f72d7fa68bd.js
18 ms
profile
212 ms
wetherburnehomes.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wetherburnehomes.com 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 Wetherburnehomes.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.
wetherburnehomes.com
Open Graph description is not detected on the main page of Wetherburnehomes. 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: