Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

perennialinn.com

perennialinn.com

Page Load Speed

963 ms in total

First Response

273 ms

Resources Loaded

517 ms

Page Rendered

173 ms

perennialinn.com screenshot

About Website

Welcome to perennialinn.com homepage info - get ready to check Perennialinn best content right away, or after learning these important things about perennialinn.com

Visit perennialinn.com

Key Findings

We analyzed Perennialinn.com page load time and found that the first response time was 273 ms and then it took 690 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

perennialinn.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.077

95/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

perennialinn.com

273 ms

sdk.js

9 ms

perennialinnlogoh.gif

99 ms

perennialflower.jpg

211 ms

1.jpg

220 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 67% of them (8 requests) were addressed to the original Perennialinn.com, 17% (2 requests) were made to Staticxx.facebook.com and 8% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (273 ms) belongs to the original domain Perennialinn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.5 kB (17%)

Content Size

106.1 kB

After Optimization

88.5 kB

In fact, the total size of Perennialinn.com main page is 106.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. 25% of websites need less resources to load. Images take 83.8 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 15.4 kB

  • Original 22.3 kB
  • After minification 20.8 kB
  • After compression 6.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. 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 15.4 kB or 69% of the original size.

Image Optimization

-3%

Potential reduce by 2.1 kB

  • Original 83.8 kB
  • After minification 81.7 kB

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. Perennialinn images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Perennialinn. According to our analytics all requests are already optimized.

Accessibility Review

perennialinn.com accessibility score

89

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

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

perennialinn.com SEO score

92

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Perennialinn.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Perennialinn.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 Perennialinn. 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: