Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

visitdenver.com

Denver Colorado Vacations & Conventions | Plan Your Trip

Page Load Speed

2.2 sec in total

First Response

64 ms

Resources Loaded

938 ms

Page Rendered

1.2 sec

visitdenver.com screenshot

About Website

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

Explore things to do, hotels, restaurants & more in Denver. Find all the info you need to start planning your trip or meeting. Download our Visitors Guide!

Visit visitdenver.com

Key Findings

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

Performance Metrics

visitdenver.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value3,150 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.043

99/100

15%

TTI (Time to Interactive)

Value28.8 s

0/100

10%

Network Requests Diagram

visitdenver.com

64 ms

104 ms

www.denver.org

17 ms

shared.css

12 ms

widget_header_cta.css

29 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Visitdenver.com, 60% (61 requests) were made to Denver.org and 27% (28 requests) were made to Assets.simpleviewinc.com. The less responsive or slowest element that took the longest time to load (210 ms) relates to the external source Fast.fonts.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 418.2 kB (55%)

Content Size

759.8 kB

After Optimization

341.6 kB

In fact, the total size of Visitdenver.com main page is 759.8 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. 60% of websites need less resources to load. HTML takes 378.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 327.0 kB

  • Original 378.1 kB
  • After minification 356.6 kB
  • After compression 51.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 327.0 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 101 B

  • Original 162.9 kB
  • After minification 162.8 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. Visit Denver images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 73.2 kB

  • Original 152.9 kB
  • After minification 152.4 kB
  • After compression 79.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 73.2 kB or 48% of the original size.

CSS Optimization

-27%

Potential reduce by 17.9 kB

  • Original 65.9 kB
  • After minification 65.9 kB
  • After compression 48.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. Visitdenver.com needs all CSS files to be minified and compressed as it can save up to 17.9 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 77 (79%)

Requests Now

97

After Optimization

20

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

Accessibility Review

visitdenver.com accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-*] attributes are not valid or misspelled

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

visitdenver.com SEO score

91

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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 Visitdenver.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 Visitdenver.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 Visit Denver. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: