Website review, no card needed

midlandtransport.com logo

midlandtransport.com website review

Visit site (opens in a new tab)Reviewed 19 November 202624 issues · 76 checks

This review found 24 issues worth fixing on midlandtransport.com, 5 of them high impact, across 76 checks. The most urgent: page weight: 11.1 MB in 48 requests. 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
998 ms775 msMay 30Nov 14801 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026860 ms
Jun 6, 2026845 ms
Jun 13, 2026860 ms
Jun 20, 2026856 ms
Jun 27, 2026851 ms
Jul 4, 2026870 ms
Jul 11, 2026893 ms
Jul 18, 2026927 ms
Jul 25, 2026966 ms
Aug 1, 2026972 ms
Aug 8, 2026920 ms
Aug 15, 2026886 ms
Aug 22, 2026855 ms
Aug 29, 2026887 ms
Sep 5, 2026903 ms
Sep 12, 2026910 ms
Sep 19, 2026901 ms
Sep 26, 2026858 ms
Oct 3, 2026824 ms
Oct 10, 2026823 ms
Oct 17, 2026830 ms
Oct 24, 2026818 ms
Oct 31, 2026815 ms
Nov 7, 2026805 ms
Nov 14, 2026801 ms
Real-visitor tap response (INP)75th percentile, phones
86 ms75 msMay 30Nov 1481 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202677 ms
Jun 6, 202676 ms
Jun 13, 202678 ms
Jun 20, 202677 ms
Jun 27, 202676 ms
Jul 4, 202678 ms
Jul 11, 202679 ms
Jul 18, 202679 ms
Jul 25, 202685 ms
Aug 1, 202682 ms
Aug 8, 202680 ms
Aug 15, 202679 ms
Aug 22, 202677 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 12, 202680 ms
Sep 19, 202680 ms
Sep 26, 202678 ms
Oct 3, 202678 ms
Oct 10, 202679 ms
Oct 17, 202679 ms
Oct 24, 202681 ms
Oct 31, 202684 ms
Nov 7, 202683 ms
Nov 14, 202681 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 midlandtransport.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix87
  • Improve image delivery

    10.2 MB

    7 images could be 10.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Hotjar, Google Tag Manager and Optanon and others), adding 10.9 MB and 244 ms of main-thread time.

  • Optimizely adds 0 ms

    0 ms

    Optimizely costs a phone 0 ms of main-thread work and 10.3 MB 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.

  • Mobile performance score: 87

    87/100

    Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    650 ms · 212 KiB

    22 files are served with short cache lifetimes, so returning visitors download them again (212 KiB).

  • Render-blocking requests

    750 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Reduce unused JavaScript

    374 KiB

    About 374 KiB of JavaScript is downloaded but never used on this page.

  • 4 long tasks on the main thread

    4 long tasks block the main thread while loading, the longest for 93 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).

  • Reduce unused CSS

    29 KiB

    About 29 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

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

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 507 ms of it running JavaScript. That is comfortably low.

  • Server response: 28 ms

    28 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 10.2 s

    10.2 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • Cumulative Layout Shift: 0.134

    0.134

    The layout shifts by 0.134 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Delivering Superior Quality Transport Services for over 55 …”. Most of its time is element render delay (1.5 s).

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user INP: 80 ms

    80 ms

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

  • 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 765 ms

    765 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 44 ms

    44 ms

    Scripts block the page for only 44 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix25
  • Page weight: 11.1 MB in 48 requests

    11.1 MB

    Your homepage downloads 11.1 MB in 48 requests on a phone: images 10.4 MB (24), scripts 626 KiB (11) and fonts 59 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Zz02MTIzYzMzMmI2YjMxMWYxOWE4YjNhN2RiMGEwYjc1ZQ== weighs 1.0 MB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    Zz02MTIzYzMzMmI2YjMxMWYxOWE4YjNhN2RiMGEwYjc1ZQ== is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (1.0 MB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image far larger than shown

    435 KiB

    1 image is downloaded at several times the size a phone draws it, for example Zz02MTIzYzMzMmI2YjMxMWYxOWE4YjNhN2RiMGEwYjc1ZQ== at 1,410 px wide, shown at 358 px. Resized copies would save about 435 KiB.

  • About 3.2 g of CO₂ per visit

    3.16 g

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

Accessibility

1 to fixGoogle 10099
  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 66 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091
  • No structured data

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

  • Meta description is long (186 characters)

    Your meta description is 186 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 105 internal links, 22 external

    The homepage links to 105 pages on midlandtransport.com and 22 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Delivering Superior Quality Transport Services for over 55 years”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Midland Transport | Transportation Services Canada & U.S.”.

  • Canonical URL set

    The canonical URL is https://www.midlandtransport.com/en/.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.midlandtransport.com/fr/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://www.midlandtransport.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 (615 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9697
  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    15 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix50
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 406 words of copy

    The homepage carries about 406 words of visible text.

2 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Register now”, “Get started” and “Join our team”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and Hotjar (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 7 cookies set on arrival

    7

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

  • 10 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 midlandtransport.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on midlandtransport.com, including 12 speed issues, 2 SEO issues and 2 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