1.6 sec in total
119 ms
1.1 sec
425 ms
Visit washingtondc.hamptoninn.com now to see the best up-to-date Washington DC Hampton Inn content for United States and also check out these interesting facts you probably never knew about washingtondc.hamptoninn.com
The Hampton Inn Washington-Downtown-Convention Center hotel has spacious guest rooms, offering a world of comfort just steps from Washington DC's best culture.
Visit washingtondc.hamptoninn.comWe analyzed Washingtondc.hamptoninn.com page load time and found that the first response time was 119 ms and then it took 1.5 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.
washingtondc.hamptoninn.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value11.3 s
0/100
25%
Value15.8 s
0/100
10%
Value18,710 ms
0/100
30%
Value0.393
26/100
15%
Value41.9 s
0/100
10%
119 ms
610 ms
27 ms
25 ms
20 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Washingtondc.hamptoninn.com, 93% (56 requests) were made to Hilton.com and 2% (1 request) were made to Hilton.cdn-v3.conductrics.net. The less responsive or slowest element that took the longest time to load (610 ms) relates to the external source Hilton.com.
Page size can be reduced by 336.7 kB (62%)
539.1 kB
202.4 kB
In fact, the total size of Washingtondc.hamptoninn.com main page is 539.1 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. 80% 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. HTML takes 347.7 kB which makes up the majority of the site volume.
Potential reduce by 271.5 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 271.5 kB or 78% of the original size.
Potential reduce by 0 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. Washington DC Hampton Inn images are well optimized though.
Potential reduce by 65.2 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 65.2 kB or 76% of the original size.
Number of requests can be reduced by 26 (51%)
51
25
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Washington DC Hampton Inn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
washingtondc.hamptoninn.com
119 ms
610 ms
dt-jSoVLlm8Db1J9D3k4nN05QFUuoFH90
27 ms
ruxitagentjs_ICA237Vfghjoqrtux_10249220905100923.js
25 ms
bde0f56f366222846a97.css
20 ms
99f6fa283cc01c95ba5f.css
20 ms
SBHYK-LK2AL-UW4L5-6RD2N-4TGQC
58 ms
4.0-26025-5.svg
94 ms
HP.svg
29 ms
washhhx-hotel-exterior-at-dusk.jpg
103 ms
king-bed-2.jpg
43 ms
king-bed-suite-1.jpg
60 ms
king-bed-studio-2.jpg
65 ms
lobby-soft-seating.jpg
63 ms
lobby-community-table.jpg
588 ms
breakfast-buffet-2.jpg
82 ms
hudcv08-0213-0185.jpg
235 ms
ye7y0687-edit2.jpg
235 ms
meeting-space.jpg
235 ms
hudcv08-0213-0177.jpg
236 ms
washhhx-patio-area.jpg
255 ms
king-bed-2.jpg
240 ms
king-bed-suite-1.jpg
235 ms
1-king-bed-accessible3.jpg
240 ms
HP.svg
236 ms
map-pin.svg
240 ms
Facebook.svg
252 ms
Twitter.svg
254 ms
Instagram.svg
255 ms
regular.woff
330 ms
light.woff
251 ms
semibold.woff
252 ms
bold.woff
254 ms
extrabold.woff
252 ms
polyfills-10e55e0652b94c94c962.js
78 ms
main-2c508b7c1b9bea60f23e.js
78 ms
webpack-29deb285d8a0b13bc9fb.js
78 ms
framework.37ae1025e3f9b771b7a6.js
77 ms
commons.c2671b8e1387ffa0db41.js
96 ms
e63f918301227c64c789373b64909dfe870bfe16.66a9887355e93f4e3dcd.js
97 ms
1ab5d5cf4c14e691986597dadadcfc05948572f0.903f8cb2216cba993fb2.js
95 ms
20feeea646f29a825b75fca590aed2315739e8f1.b1a1298103f79734808a.js
93 ms
e44323d5e40d1deaed1ea5306f763ca6064f0d5f.f2d2999e11b6157627e9.js
94 ms
da05b30c8ea60e394ad25770a9e57344b44a7e04.61b1f0dfa045c62483f7.js
99 ms
_app-d9c37b6b46d1967066d9.js
98 ms
686c30a1.9335db467d2e9f96cc53.js
98 ms
3f868408.4ed8347ed5b235adb0ca.js
97 ms
e971612a.23b4597ddd4fd29438df.js
238 ms
6bbd447f15c7a56c11c2528d86a10f4d7eae9d6f.98c76990349854c28c87.js
101 ms
c469d9ab254c0fdde3dbe44523df86a2ccf22c62.088b7a1c3c121eb79990.js
100 ms
1f1b179f8f806bf2e42fda4f88339751145cd6ab.8a3a3d359e76f3edac69.js
100 ms
e9ad643eb5676480a2807db733ff4eef2272ec6b.788ebc064daa449e9390.js
232 ms
9446d4cd03afe3e7aa4f838192850ed63f16e97a.e47248cbe09d3346ce85.js
237 ms
695ba57f7b5443bbca30da9748f72b64f6d24e1b.df9cbead2cf8a73eb8af.js
234 ms
cb338c519699498e8dafe230a9a7296ac346d5e4.29b0de5b5709c277369a.js
233 ms
63995b0d5c60f2e385c55895e7bceeeca449458a.80aa46ae8e87f0748b87.js
236 ms
%5BhotelSlug%5D-6a29aed578de8da811b9.js
239 ms
_buildManifest.js
237 ms
_ssgManifest.js
269 ms
BAhEz4B
236 ms
washingtondc.hamptoninn.com accessibility score
washingtondc.hamptoninn.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
washingtondc.hamptoninn.com SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Washingtondc.hamptoninn.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 Washingtondc.hamptoninn.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.
washingtondc.hamptoninn.com
Open Graph description is not detected on the main page of Washington DC Hampton Inn. 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: