Tools & Wizards About Us
metra.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

metra.com

Find Next Departure | Service Alerts | Schedules & Maps

Page Load Speed

2.8 sec in total

First Response

12 ms

Resources Loaded

2 sec

Page Rendered

743 ms

metra.com screenshot

About Website

Welcome to metra.com homepage info - get ready to check Metra best content for United States right away, or after learning these important things about metra.com

Metra train departure times, services alerts, schedules and maps, click here to get started with Metra.

Visit metra.com

Key Findings

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

Performance Metrics

metra.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

metra.com

12 ms

metra.com

673 ms

fbevents.js

75 ms

gtm.js

106 ms

js

135 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 40% of them (22 requests) were addressed to the original Metra.com, 7% (4 requests) were made to Live.rezync.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (673 ms) belongs to the original domain Metra.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.3 kB (2%)

Content Size

5.5 MB

After Optimization

5.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Metra.com main page is 5.5 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. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 113.5 kB

  • Original 136.4 kB
  • After minification 110.4 kB
  • After compression 22.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. This page needs HTML code to be minified as it can gain 26.0 kB, which is 19% 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 113.5 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 17.1 kB

  • Original 4.5 MB
  • After minification 4.5 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. Metra images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 783.7 kB
  • After minification 783.7 kB
  • After compression 782.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 524 B

  • Original 67.5 kB
  • After minification 67.5 kB
  • After compression 67.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. Metra.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (56%)

Requests Now

48

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

metra.com

metra.com

12 ms

metra.com

metra.com

673 ms

fbevents.js

fbevents.js

75 ms

gtm.js

gtm.js

106 ms

js

js

135 ms

tc.min.js

tc.min.js

164 ms

css_vRNR55W51o9yPZJJl-Q7FbhXjPf0cAdTrQodlsJyAnQ.css

css_vRNR55W51o9yPZJJl-Q7FbhXjPf0cAdTrQodlsJyAnQ.css

36 ms

css_EnvVKt1W3gUIFm5t5s-PT10EN0cLAdj8MxvyiQaKkD4.css

css_EnvVKt1W3gUIFm5t5s-PT10EN0cLAdj8MxvyiQaKkD4.css

41 ms

all.js

all.js

162 ms

v4-shims.js

v4-shims.js

196 ms

CroppedLogo.png

CroppedLogo.png

63 ms

logo.svg

logo.svg

28 ms

STA0472_Metra_Exterior_front_cabin.jpg

STA0472_Metra_Exterior_front_cabin.jpg

60 ms

Get%20Access%20%28insta%29.png

Get%20Access%20%28insta%29.png

65 ms

rider.jpg

rider.jpg

65 ms

crowd.jpg

crowd.jpg

98 ms

css

css

122 ms

element.js

element.js

186 ms

js_cnYTbRTtZsM1KeY2sKf3ELaLnbuUBb--2DU8k2pTjoU.js

js_cnYTbRTtZsM1KeY2sKf3ELaLnbuUBb--2DU8k2pTjoU.js

54 ms

js

js

132 ms

Search.svg

Search.svg

95 ms

HamburgerMenu.svg

HamburgerMenu.svg

72 ms

chevron-right-red.svg

chevron-right-red.svg

79 ms

FacebookRed.svg

FacebookRed.svg

73 ms

XTwitterRed.svg

XTwitterRed.svg

69 ms

InstagramRed.svg

InstagramRed.svg

77 ms

YouTubeRed.svg

YouTubeRed.svg

70 ms

LinkedInRed.svg

LinkedInRed.svg

74 ms

DSC_2442-001_adma9q.jpg

DSC_2442-001_adma9q.jpg

85 ms

chevron-down-purple.svg

chevron-down-purple.svg

74 ms

required.svg

required.svg

75 ms

ca.html

ca.html

445 ms

font

font

150 ms

sync

sync

119 ms

font

font

30 ms

pixel

pixel

128 ms

Pug

Pug

117 ms

cksync.php

cksync.php

146 ms

186 ms

360947.gif

360947.gif

157 ms

rocketfuel_sync

rocketfuel_sync

397 ms

sync

sync

123 ms

g.pixel

g.pixel

133 ms

sd

sd

12 ms

demconf.jpg

demconf.jpg

4 ms

pixel

pixel

15 ms

cm

cm

258 ms

rum

rum

27 ms

sync

sync

19 ms

bounce

bounce

17 ms

pixel

pixel

72 ms

pixel

pixel

143 ms

sync

sync

51 ms

pixel

pixel

70 ms

sync

sync

34 ms

Accessibility Review

metra.com accessibility score

77

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

ARIA IDs are not unique

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

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

Best Practices

metra.com best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

metra.com SEO score

84

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

metra.com

Open Graph description is not detected on the main page of Metra. 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: