54.3 sec in total
127 ms
54.1 sec
150 ms
Visit hampton.com now to see the best up-to-date Hampton content for Nigeria and also check out these interesting facts you probably never knew about hampton.com
Book hotel rooms with Hampton by Hilton. Enjoy a great stay at a great value, and experience Hamptonality.
Visit hampton.comWe analyzed Hampton.com page load time and found that the first response time was 127 ms and then it took 54.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
hampton.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value10.0 s
0/100
25%
Value10.8 s
6/100
10%
Value7,160 ms
0/100
30%
Value0.336
33/100
15%
Value28.2 s
0/100
10%
127 ms
9225 ms
13 ms
8 ms
10040 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hampton.com, 35% (54 requests) were made to Hamptoninn3.hilton.com and 9% (14 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (18.2 sec) relates to the external source Hamptoninn3.hilton.com.
Page size can be reduced by 2.7 MB (13%)
20.6 MB
17.9 MB
In fact, the total size of Hampton.com main page is 20.6 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 18.4 MB which makes up the majority of the site volume.
Potential reduce by 78.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. This page needs HTML code to be minified as it can gain 12.0 kB, which is 12% 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 78.9 kB or 79% of the original size.
Potential reduce by 1.1 MB
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. Hampton images are well optimized though.
Potential reduce by 1.4 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.4 MB or 71% of the original size.
Potential reduce by 172.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. Hampton.com needs all CSS files to be minified and compressed as it can save up to 172.6 kB or 83% of the original size.
Number of requests can be reduced by 88 (68%)
130
42
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hampton. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
hampton.com
127 ms
index.html
9225 ms
737eeb8b-e71c-4905-83c4-8ddaf4719c5e.css
13 ms
07e72eb4-de7f-4caf-97d6-4a8a8a47bb7f.css
8 ms
common.min.css
10040 ms
global_xa.css
9071 ms
sayt.min.css
9077 ms
search_widget.min.css
8080 ms
styles.min.css
10080 ms
connector.js
48 ms
tracking.comp.min.js
9159 ms
satelliteLib-5f15f2949f2a761b35db03f2b389a11d61654c4e.js
9 ms
mmcore.js
97 ms
jquery.min.js
17124 ms
core.comp.min.js
18157 ms
hp.comp.min.js
18119 ms
addthis_widget.js
9 ms
dataTrackingFunctions.dev.min.js
17222 ms
sample.jpeg
167 ms
honors_icons_logo_hilton_honors_white.svg
41 ms
logo_brand_HP.gif
43 ms
HX_hx_3day.jpg
184 ms
HX_2k_points.jpg
187 ms
HX_hx_trophy_2.jpg
259 ms
HX_waffles_3.jpg
274 ms
HX_doubleyedo_4.jpg
335 ms
HX_triplerday_5.jpg
351 ms
logo-adchoices.png
374 ms
satellite-544ab9f4314c97bda3000979.js
12 ms
satellite-544abd31314c97bda3000988.js
12 ms
16 ms
rd
36 ms
dock_icon_arrow_down.gif
322 ms
nav_bknd.gif
344 ms
logo_bknd.jpg
363 ms
find_a_hotel_nav_bknd.gif
384 ms
find_hotel_arrow_rt.gif
405 ms
globe.png
427 ms
ui-icons_222222_256x240.png
447 ms
find_a_hotel_form_bknd.gif
470 ms
link_icon.png
488 ms
cta_arrow_white.png
500 ms
id
73 ms
gallery_content_bknd.png
510 ms
gallery_active_bknd.png
534 ms
social-icons.png
45 ms
cta_secondary.jpg
44 ms
submit_btn.jpg
43 ms
footer_bknd.jpg
81 ms
logo_brandbar.png
120 ms
brand_tooltip_arrow.png
79 ms
activityi;src=2013561;type=hampt136;cat=hpcom188;u3=HP;u18=en;u14=null;u19=null;ord=7421263898722.827
184 ms
lb
160 ms
530
31 ms
43 ms
tre
267 ms
beacon
113 ms
hbjs
163 ms
17 ms
bounce
14 ms
async_usersync.html
23 ms
74 ms
trackconversion
9 ms
ps
17 ms
pixel
19 ms
80 ms
src=5339326;type=invmedia;cat=jkkvqwtd;u1=1;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=1
77 ms
ibs:dpid=22069&dpuuid=2010768254250
8 ms
hilton-us
104 ms
x22561r8320293
33 ms
394499.gif
5 ms
sd
11 ms
76 ms
102 ms
cmap
19 ms
tap.php
7 ms
12 ms
18456
101 ms
view
37 ms
tre
210 ms
usrm-test
38 ms
rum
231 ms
51 ms
70 ms
tap.php
32 ms
pixel
48 ms
pixel
47 ms
match
36 ms
match
66 ms
match
151 ms
match
149 ms
44 ms
35 ms
14 ms
rum
9 ms
null
7 ms
13 ms
153 ms
jsonResourceBundleGroup.json
6001 ms
63 ms
find_hotel_arrow.gif
69 ms
satellite-57b20d0c64746d4d41000694.js
53 ms
notice
363 ms
satellite-56698e4164746d62d8001815.js
48 ms
satellite-598c35d564746d2c220013aa.js
46 ms
satellite-598c391364746d57080025cb.js
47 ms
satellite-598c35d564746d2c220013ab.html
47 ms
satellite-57d1c85964746d3238000835.js
44 ms
satellite-5733713c64746d2dff002873.js
42 ms
s-code-contents-cf588c401b906b1c24383909bd30f3ba583cb70b.js
42 ms
satellite-582cfe6f64746d064e004f39.html
39 ms
horizontalBarScrolling.phtml
6002 ms
searchForm.json
6000 ms
datepicker.json
6009 ms
jsLoader.js
8044 ms
_ate.track.config_resp
20 ms
300lo.json
48 ms
ps
37 ms
23784
129 ms
sh.48536d49e4da3bdba54606b4.html
49 ms
80013
253 ms
fbevents.js
86 ms
conversen-SDK.js
72 ms
247px.js
59 ms
json
39 ms
Pug
42 ms
usersync
36 ms
8f3909c0b249.js
34 ms
s95663087021093
16 ms
Pix-1x1.gif
41 ms
247loader.js
8 ms
ps
9 ms
pxt.js
341 ms
689187874494318
16 ms
sync
102 ms
20 ms
pixel
14 ms
pixel
11 ms
src=4838412;type=sales;cat=vc1esw10;qty=1;cost=0;u1=[tid];u16=;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=[OrderID]
66 ms
pixel
17 ms
AdX
48 ms
brand.phtml
6000 ms
calendar.gif
73 ms
gallery.js
8058 ms
HX_hx_3day.jpg
138 ms
HX_2k_points.jpg
80 ms
HX_hx_trophy_2.jpg
170 ms
HX_waffles_3.jpg
173 ms
HX_doubleyedo_4.jpg
179 ms
HX_triplerday_5.jpg
216 ms
409b4bec-c67e-4764-a141-054db8df81d2.woff
2 ms
print.min.css
10051 ms
satellite-594361e664746d6ede00a745.js
9 ms
satellite-5886240664746d6199009c44.html
8 ms
hampton.com accessibility score
hampton.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
Missing source maps for large first-party JavaScript
hampton.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
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hampton.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 Hampton.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
hampton.com
Open Graph description is not detected on the main page of Hampton. 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: