Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

hampton.com

Hampton by Hilton Hotel Rooms and Reservations

Page Load Speed

54.3 sec in total

First Response

127 ms

Resources Loaded

54.1 sec

Page Rendered

150 ms

hampton.com screenshot

About Website

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.com

Key Findings

We 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.

Performance Metrics

hampton.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value7,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.336

33/100

15%

TTI (Time to Interactive)

Value28.2 s

0/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 2.7 MB (13%)

Content Size

20.6 MB

After Optimization

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.

HTML Optimization

-79%

Potential reduce by 78.9 kB

  • Original 99.3 kB
  • After minification 87.3 kB
  • After compression 20.4 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.

Image Optimization

-6%

Potential reduce by 1.1 MB

  • Original 18.4 MB
  • After minification 17.3 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.

JavaScript Optimization

-71%

Potential reduce by 1.4 MB

  • Original 2.0 MB
  • After minification 1.9 MB
  • After compression 577.8 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 1.4 MB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 172.6 kB

  • Original 207.0 kB
  • After minification 192.2 kB
  • After compression 34.4 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.

Requests Breakdown

Number of requests can be reduced by 88 (68%)

Requests Now

130

After Optimization

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.

Accessibility Review

hampton.com accessibility score

100

Accessibility Issues

Best Practices

hampton.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

hampton.com SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: