Website review, no card needed

metrolinktrains.com logo

metrolinktrains.com website review

Visit site (opens in a new tab)Reviewed 25 October 202642 issues · 84 checks

This review found 42 issues worth fixing on metrolinktrains.com, 14 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.4 s1.3 sMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
246 ms153 msMay 2Oct 17230 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026164 ms
May 9, 2026169 ms
May 16, 2026173 ms
May 23, 2026182 ms
May 30, 2026194 ms
Jun 6, 2026204 ms
Jun 13, 2026211 ms
Jun 20, 2026212 ms
Jun 27, 2026209 ms
Jul 4, 2026206 ms
Jul 11, 2026208 ms
Jul 18, 2026209 ms
Jul 25, 2026212 ms
Aug 1, 2026218 ms
Aug 8, 2026220 ms
Aug 15, 2026222 ms
Aug 22, 2026222 ms
Aug 29, 2026221 ms
Sep 5, 2026218 ms
Sep 12, 2026217 ms
Sep 19, 2026220 ms
Sep 26, 2026225 ms
Oct 3, 2026232 ms
Oct 10, 2026235 ms
Oct 17, 2026230 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of metrolinktrains.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. metrolinktrains.com at 0.4 s0.4 s
  2. metrolinktrains.com at 0.8 s0.8 s
  3. metrolinktrains.com at 1.1 s1.1 s
  4. metrolinktrains.com at 1.5 s1.5 s
  5. metrolinktrains.com at 1.9 s1.9 s
  6. metrolinktrains.com at 2.3 s2.3 s
  7. metrolinktrains.com at 2.6 s2.6 s
  8. metrolinktrains.com at 3.0 s3.0 s

Speed

9 to fix55
  • Reduce unused JavaScript

    2.3 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Use efficient cache lifetimes

    1.6 s · 1.3 MB

    45 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

  • Improve image delivery

    1.1 s · 1.4 MB

    8 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Render-blocking requests

    2.0 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1.6 MB and 1.1 s of main-thread time.

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55 (desktop: 68). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    750 ms · 167 KiB

    About 167 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Google Tag Manager adds 411 ms

    411 ms

    Google Tag Manager costs a phone 411 ms of main-thread work and 559 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 2.5 s

    A phone's processor spends 2.5 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Legacy JavaScript

    150 ms · 66 KiB

    Polyfills for old browsers add 66 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 166 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 7.9 s

    7.9 s

    Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies and similar technologies to impro…”.

  • Time to Interactive: 18.6 s

    18.6 s

    The page becomes fully interactive after 18.6 s. Good is under 3.8 s.

  • First Contentful Paint: 3.5 s

    3.5 s

    The first text or image appears after 3.5 s on a phone. Good is under 1.8 s.

  • Real-user INP: 263 ms

    263 ms

    Real visitors wait 263 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 40% slower for real visitors

    +40%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 164 ms to 230 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 5.0 s

    5.0 s

    Visually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 410 ms

    410 ms

    Scripts block taps and scrolling for 410 ms in total while the page loads. Good is under 200 ms.

  • 18 images without width and height

    18 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 490 ms

    490 ms

    Real visitors wait 490 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.009

    0.009

    The layout barely moves while loading (CLS 0.009, good is under 0.1).

Images and page weight

3 to fix35
  • Page weight: 4.0 MB in 130 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 130 requests on a phone: scripts 2.0 MB (39), images 1.6 MB (34) and stylesheets 184 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    homeslider2-arrow-metrolink.jpg weighs 691 KiB. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    1.1 MB

    5 images are downloaded at several times the size a phone draws them, for example homeslider2-arrow-metrolink.jpg at 3,420 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

  • 3 images below the first screen load straight away

    3 images further down the page (107 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.14 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 136.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 9794
  • Orphan list items

    Some list items are not inside a list.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9276
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (20 characters)

    Your title is only 20 characters: “Welcome to Metrolink”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 84 internal links, 9 external

    The homepage links to 84 pages on metrolinktrains.com and 9 external pages.

5 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “Discover Southern California with Metrolink trains - convenient, reliable, and eco-friendly travel. Plan your trip toda…”.

  • Canonical URL set

    The canonical URL is https://metrolinktrains.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://metrolinktrains.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://metrolinktrains.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (914 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://metrolinktrains.com/news/alert-details-page is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://metrolinktrains.com/community-main/welcome, https://metrolinktrains.com/news and https://metrolinktrains.com/ticketsOverview/where-to-buy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://metrolinktrains.com/news/alert-details-page and https://metrolinktrains.com/train_status have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 71 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 14 small tap targets

    14 of 47 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,085 words of copy

    The homepage carries about 1,085 words of visible text.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Where To Buy”, “Get schedule” and “Learn More and Download”.

  • 2 short forms

    2 short forms (5 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 4 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 41 other companies contacted

    Loading the homepage contacts 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at metrolinktrains.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Vue.js
Analytics
Google Tag Manager

Company

Headquarters
Wilshire Grand Center

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on metrolinktrains.com, including 18 speed issues, 5 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25