Tools & Wizards About Us

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

qualityinnflorissant.com

Hotels in Florissant MO | Quality Inn and Suites St. Louis | Florissant, Missouri Hotel

Page Load Speed

1.4 sec in total

First Response

9 ms

Resources Loaded

777 ms

Page Rendered

589 ms

About Website

Welcome to qualityinnflorissant.com homepage info - get ready to check Quality Inn Florissant best content right away, or after learning these important things about qualityinnflorissant.com

Official Site. Best Rate Guarantee. Great location for Florissant Missouri Hotels and Motels in Florissant- The Quality Inn and Suites St. Louis provides accommodations near downtown

Visit qualityinnflorissant.com

Key Findings

We analyzed Qualityinnflorissant.com page load time and found that the first response time was 9 ms and then it took 1.4 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.

Performance Metrics

qualityinnflorissant.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.127

82/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

qualityinnflorissant.com

9 ms

www.qualityinnflorissant.com

70 ms

style.css

11 ms

lunar.css

51 ms

custom.css

55 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 46% of them (40 requests) were addressed to the original Qualityinnflorissant.com, 20% (17 requests) were made to Myeres.com and 15% (13 requests) were made to Tripadvisor.com. The less responsive or slowest element that took the longest time to load (494 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 603.9 kB (23%)

Content Size

2.6 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qualityinnflorissant.com main page is 2.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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 49.7 kB

  • Original 61.7 kB
  • After minification 49.0 kB
  • After compression 12.0 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.6 kB, which is 20% 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 49.7 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 9.9 kB

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

JavaScript Optimization

-74%

Potential reduce by 245.8 kB

  • Original 331.9 kB
  • After minification 261.7 kB
  • After compression 86.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 245.8 kB or 74% of the original size.

CSS Optimization

-84%

Potential reduce by 298.6 kB

  • Original 354.6 kB
  • After minification 298.4 kB
  • After compression 56.0 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. Qualityinnflorissant.com needs all CSS files to be minified and compressed as it can save up to 298.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (52%)

Requests Now

82

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Quality Inn Florissant. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

qualityinnflorissant.com accessibility score

72

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

qualityinnflorissant.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Qualityinnflorissant.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 Qualityinnflorissant.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 data is detected on the main page of Quality Inn Florissant. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: