Tools & Wizards About Us

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

1872inn.com

1872 Inn - Boutique Hotel Lodging in West Yellowstone, Montana

Page Load Speed

1.4 sec in total

First Response

108 ms

Resources Loaded

1 sec

Page Rendered

251 ms

About Website

Visit 1872inn.com now to see the best up-to-date 1872 Inn content and also check out these interesting facts you probably never knew about 1872inn.com

Just steps away from the West Entrance to Yellowstone National Park, 1872 Inn is the ideal location for your Yellowstone vacation.

Visit 1872inn.com

Key Findings

We analyzed 1872inn.com page load time and found that the first response time was 108 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

1872inn.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

www.1872inn.com

108 ms

gtm.js

68 ms

js

120 ms

css

84 ms

style.css

118 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 15% of them (4 requests) were addressed to the original 1872inn.com, 23% (6 requests) were made to Media.mybnbwebsite.com and 12% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (271 ms) relates to the external source Sdk.videeo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.9 kB (5%)

Content Size

2.7 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of 1872inn.com main page is 2.7 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. 35% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 60.8 kB

  • Original 83.9 kB
  • After minification 82.7 kB
  • After compression 23.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 60.8 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 20.9 kB

  • Original 2.2 MB
  • After minification 2.2 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. 1872 Inn images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 65.3 kB

  • Original 466.2 kB
  • After minification 464.3 kB
  • After compression 400.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 65.3 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (64%)

Requests Now

22

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1872 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 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

1872inn.com accessibility score

100

Accessibility Issues

Best Practices

1872inn.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

1872inn.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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1872inn.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 1872inn.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of 1872 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: