Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

rockies.com

Official Colorado Rockies Website | MLB.com

Page Load Speed

3.4 sec in total

First Response

96 ms

Resources Loaded

2.9 sec

Page Rendered

427 ms

rockies.com screenshot

About Website

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

The official website of the Colorado Rockies with the most up-to-date information on scores, schedule, stats, tickets, and team news.

Visit rockies.com

Key Findings

We analyzed Rockies.com page load time and found that the first response time was 96 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

rockies.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value46.1 s

0/100

25%

SI (Speed Index)

Value56.9 s

0/100

10%

TBT (Total Blocking Time)

Value24,570 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value88.2 s

0/100

10%

Network Requests Diagram

rockies.com

96 ms

index.jsp

40 ms

global.css

16 ms

col.css

33 ms

jquery-ui-1.8.custom.css

19 ms

Our browser made a total of 372 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Rockies.com, 64% (239 requests) were made to Colorado.rockies.mlb.com and 10% (39 requests) were made to Mlb.mlb.com. The less responsive or slowest element that took the longest time to load (921 ms) relates to the external source Ui.bamstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (54%)

Content Size

4.7 MB

After Optimization

2.1 MB

In fact, the total size of Rockies.com main page is 4.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. 85% 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. Javascripts take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 318.2 kB

  • Original 368.6 kB
  • After minification 307.3 kB
  • After compression 50.5 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 61.3 kB, which is 17% 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 318.2 kB or 86% of the original size.

Image Optimization

-12%

Potential reduce by 194.0 kB

  • Original 1.6 MB
  • After minification 1.4 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. Obviously, Rockies needs image optimization as it can save up to 194.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 1.8 MB

  • Original 2.4 MB
  • After minification 1.8 MB
  • After compression 614.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 1.8 MB or 74% of the original size.

CSS Optimization

-83%

Potential reduce by 241.5 kB

  • Original 290.3 kB
  • After minification 246.5 kB
  • After compression 48.8 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. Rockies.com needs all CSS files to be minified and compressed as it can save up to 241.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 215 (60%)

Requests Now

359

After Optimization

144

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

Accessibility Review

rockies.com accessibility score

69

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-hidden="true"] elements contain focusable descendents

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

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

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