Tools & Wizards About Us
rays.mlb.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

rays.mlb.com

Official Tampa Bay Rays Website | MLB.com

Page Load Speed

1.7 sec in total

First Response

157 ms

Resources Loaded

1.2 sec

Page Rendered

383 ms

rays.mlb.com screenshot

About Website

Click here to check amazing Rays MLB content for United States. Otherwise, check out these important facts you probably never knew about rays.mlb.com

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

Visit rays.mlb.com

Key Findings

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

Performance Metrics

rays.mlb.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value61.9 s

0/100

25%

SI (Speed Index)

Value45.3 s

0/100

10%

TBT (Total Blocking Time)

Value30,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value195.1 s

0/100

10%

Network Requests Diagram

rays

157 ms

Ixnon6Nk9xou2jR8_m5H0h8H4q4.js

73 ms

mlb-okta.js

111 ms

makeTFL.js

88 ms

VisitorAPI.js

87 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Rays.mlb.com, 24% (26 requests) were made to Builds.mlbstatic.com and 5% (5 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (451 ms) relates to the external source Builds.mlbstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (58%)

Content Size

1.9 MB

After Optimization

796.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rays.mlb.com main page is 1.9 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. Only a small number of websites need less resources to load. HTML takes 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 853.2 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 184.8 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 853.2 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 22 B

  • Original 73.2 kB
  • After minification 73.1 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. Rays MLB images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 264.2 kB

  • Original 798.5 kB
  • After minification 798.5 kB
  • After compression 534.3 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 264.2 kB or 33% of the original size.

CSS Optimization

-5%

Potential reduce by 215 B

  • Original 4.5 kB
  • After minification 4.5 kB
  • After compression 4.3 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. Rays.mlb.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

101

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rays

rays

157 ms

Ixnon6Nk9xou2jR8_m5H0h8H4q4.js

Ixnon6Nk9xou2jR8_m5H0h8H4q4.js

73 ms

mlb-okta.js

mlb-okta.js

111 ms

makeTFL.js

makeTFL.js

88 ms

VisitorAPI.js

VisitorAPI.js

87 ms

at.js

at.js

98 ms

AppMeasurement-mlb.js

AppMeasurement-mlb.js

90 ms

AppMeasurement.js

AppMeasurement.js

95 ms

adobe-client-data-layer.min.js

adobe-client-data-layer.min.js

95 ms

launch-0febec0c5fac.min.js

launch-0febec0c5fac.min.js

97 ms

mlb.css

mlb.css

92 ms

7eae26a6777bacfb.css

7eae26a6777bacfb.css

92 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

98 ms

webpack-906465828da41bc3.js

webpack-906465828da41bc3.js

87 ms

framework-fc1f2e8247ad02c2.js

framework-fc1f2e8247ad02c2.js

99 ms

main-013ed5e937cbafef.js

main-013ed5e937cbafef.js

96 ms

_app-4d25c2dcfbbfd04a.js

_app-4d25c2dcfbbfd04a.js

326 ms

78537f27-42185e0a77dadfff.js

78537f27-42185e0a77dadfff.js

97 ms

952ae657-9bd842404a4da910.js

952ae657-9bd842404a4da910.js

335 ms

e999873e-563f307a5602f302.js

e999873e-563f307a5602f302.js

101 ms

a29ae703-cf98c0f8bbf396d4.js

a29ae703-cf98c0f8bbf396d4.js

102 ms

faf0dfaa-e58ba85f1d6ab56d.js

faf0dfaa-e58ba85f1d6ab56d.js

102 ms

9922685e-ef125a69f5cfc779.js

9922685e-ef125a69f5cfc779.js

321 ms

9b61e6c5-afd3c196a6ae48d4.js

9b61e6c5-afd3c196a6ae48d4.js

321 ms

b548615e-77a905354a612119.js

b548615e-77a905354a612119.js

319 ms

2edb282b-b8f4863366339abc.js

2edb282b-b8f4863366339abc.js

321 ms

66dee5eb-1c9ac7fb197a1179.js

66dee5eb-1c9ac7fb197a1179.js

323 ms

20ccc6d2-22e02c5c9f239c32.js

20ccc6d2-22e02c5c9f239c32.js

321 ms

a6c7d93c-2bff0f5b3ea8d817.js

a6c7d93c-2bff0f5b3ea8d817.js

376 ms

26b4518c-4f50042f86a9d7da.js

26b4518c-4f50042f86a9d7da.js

380 ms

0ef9dd76-5230562dc221b756.js

0ef9dd76-5230562dc221b756.js

366 ms

96459ee1-323f8a7fca3a349a.js

96459ee1-323f8a7fca3a349a.js

375 ms

557-89c8527f71fa00cf.js

557-89c8527f71fa00cf.js

451 ms

%5B%5B...path%5D%5D-45a7462e0b1f67e9.js

%5B%5B...path%5D%5D-45a7462e0b1f67e9.js

426 ms

_buildManifest.js

_buildManifest.js

419 ms

_ssgManifest.js

_ssgManifest.js

426 ms

_middlewareManifest.js

_middlewareManifest.js

428 ms

t139-global-properties-t139-background-skins-t139-base-palette.css

t139-global-properties-t139-background-skins-t139-base-palette.css

68 ms

id

id

319 ms

gtm.js

gtm.js

384 ms

tags.js

tags.js

317 ms

t139_header_masthead_tagline.svg

t139_header_masthead_tagline.svg

315 ms

t139_url_logo.svg

t139_url_logo.svg

254 ms

t139-bodyBackgroundSkin.jpg

t139-bodyBackgroundSkin.jpg

355 ms

139.svg

139.svg

172 ms

110.svg

110.svg

171 ms

111.svg

111.svg

169 ms

147.svg

147.svg

168 ms

139.svg

139.svg

167 ms

141.svg

141.svg

173 ms

145.svg

145.svg

185 ms

114.svg

114.svg

187 ms

116.svg

116.svg

187 ms

118.svg

118.svg

188 ms

142.svg

142.svg

183 ms

117.svg

117.svg

185 ms

108.svg

108.svg

225 ms

133.svg

133.svg

230 ms

136.svg

136.svg

225 ms

140.svg

140.svg

227 ms

144.svg

144.svg

229 ms

146.svg

146.svg

227 ms

121.svg

121.svg

234 ms

143.svg

143.svg

236 ms

120.svg

120.svg

238 ms

112.svg

112.svg

233 ms

113.svg

113.svg

236 ms

158.svg

158.svg

237 ms

134.svg

134.svg

241 ms

138.svg

138.svg

269 ms

109.svg

109.svg

248 ms

115.svg

115.svg

251 ms

119.svg

119.svg

241 ms

135.svg

135.svg

238 ms

137.svg

137.svg

269 ms

139.svg

139.svg

272 ms

141.svg

141.svg

271 ms

1.svg

1.svg

349 ms

bgca.svg

bgca.svg

351 ms

proxima-nova-regular.woff

proxima-nova-regular.woff

348 ms

proxima-nova-medium.woff

proxima-nova-medium.woff

192 ms

proxima-nova-light.woff

proxima-nova-light.woff

195 ms

proxima-nova-thin.woff

proxima-nova-thin.woff

234 ms

proxima-nova-semibold.woff

proxima-nova-semibold.woff

233 ms

proxima-nova-bold.woff

proxima-nova-bold.woff

234 ms

dest5.html

dest5.html

182 ms

id

id

176 ms

proxima-nova-extrabold.woff

proxima-nova-extrabold.woff

225 ms

proxima-nova-black.woff

proxima-nova-black.woff

218 ms

datadog-rum.js

datadog-rum.js

184 ms

gtm.js

gtm.js

134 ms

gtm.js

gtm.js

139 ms

ibs:dpid=411&dpuuid=ZkqGggAAAKq38gN-

ibs:dpid=411&dpuuid=ZkqGggAAAKq38gN-

45 ms

125 ms

otSDKStub.js

otSDKStub.js

169 ms

otCCPAiab.js

otCCPAiab.js

190 ms

ibs:dpid=21&dpuuid=213660604887013476944

ibs:dpid=21&dpuuid=213660604887013476944

23 ms

image-placeholder.svg

image-placeholder.svg

16 ms

MIN-70730.js

MIN-70730.js

59 ms

chartbeat_video.js

chartbeat_video.js

33 ms

chartbeat_mab.js

chartbeat_mab.js

60 ms

delivery

delivery

122 ms

87e3b067-33e7-4a28-84ad-4aaeb74b4d5a.json

87e3b067-33e7-4a28-84ad-4aaeb74b4d5a.json

38 ms

dnsfeed

dnsfeed

226 ms

ping

ping

20 ms

location

location

30 ms

mab

mab

10 ms

otBannerSdk.js

otBannerSdk.js

22 ms

en.json

en.json

24 ms

ibs:dpid=477&dpuuid=a1e5385eee1a55e9562171d33c4c305df37d313032c9954a25876219e3acc4ddb0da87c991749652

ibs:dpid=477&dpuuid=a1e5385eee1a55e9562171d33c4c305df37d313032c9954a25876219e3acc4ddb0da87c991749652

6 ms

Accessibility Review

rays.mlb.com accessibility score

82

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

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

Low

No form fields have multiple labels

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

rays.mlb.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

rays.mlb.com SEO score

84

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 Rays.mlb.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 Rays.mlb.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

rays.mlb.com

Open Graph data is detected on the main page of Rays MLB. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: