Website review, no card needed

abrismtl.ca logo

abrismtl.ca website review

Visit site (opens in a new tab)Reviewed 1 November 202625 issues · 70 checks

This review found 25 issues worth fixing on abrismtl.ca, 9 of them high impact, across 70 checks. The most urgent: main-thread work: 7.8 s. 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

Full-page screenshot of abrismtl.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix69
  • Main-thread work: 7.8 s

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

  • Mobile performance score: 69

    69/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, loox.io and JSDelivr CDN and others), adding 1.4 MB and 827 ms of main-thread time.

  • Shopify adds 685 ms

    685 ms

    Shopify costs a phone 685 ms of main-thread work and 1.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.

  • Render-blocking requests

    750 ms

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

  • Reduce unused JavaScript

    650 KiB

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

  • Reduce unused CSS

    300 ms · 77 KiB

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

  • 2,368 HTML elements

    The page has 2,368 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    150 ms · 53 KiB

    3 images could be 53 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    35 KiB

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

  • Use efficient cache lifetimes

    25 KiB

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

  • 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: 21 ms

    21 ms

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

Core Web Vitals

4 to fix67
  • Largest Contentful Paint: 6.2 s

    6.2 s

    Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 12.6 s

    12.6 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Total Blocking Time: 207 ms

    207 ms

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 309 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 309 requests on a phone: scripts 1.5 MB (176), other files 806 KiB (87) and images 638 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (53 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.95 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8893
  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 10 links without text

    10 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • 2 H1 headlines

    There are 2 <h1> headlines (“Abris MTL” and “L'abri d'auto pour nos hivers.”). One clear main headline is easier for people and search engines.

  • 49 internal links, 5 external

    The homepage links to 49 pages on abrismtl.ca and 5 external pages.

7 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Vente et location d’abris d’auto, installation et démontage à Laval, sur la Rive-Nord et la Rive-Sud du Grand Montréal.…”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Abris d’auto – Vente et services à Laval et Montréal | Abris MTL”.

  • Canonical URL set

    The canonical URL is https://abrismtl.ca/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://abrismtl.ca/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://abrismtl.ca/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 (1,387 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65
  • 4 linked pages are broken

    Your homepage links to https://abrismtl.ca/products/abri-simple, https://abrismtl.ca/products/abri-double, https://abrismtl.ca/pages/secteurs-desservis and https://abrismtl.ca/policies/contact-information, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 6 pages without a meta description

    https://abrismtl.ca/policies/shipping-policy, https://abrismtl.ca/policies/refund-policy, https://abrismtl.ca/policies/subscription-policy, https://abrismtl.ca/policies/privacy-policy, https://abrismtl.ca/policies/terms-of-service and https://abrismtl.ca/policies/legal-notice have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://abrismtl.ca/policies/shipping-policy, https://abrismtl.ca/policies/refund-policy, https://abrismtl.ca/policies/subscription-policy, https://abrismtl.ca/policies/privacy-policy, https://abrismtl.ca/policies/terms-of-service and https://abrismtl.ca/policies/legal-notice 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 18 found) and read each the way a search engine does.

4 checks passed
  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    8 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact” and “Schedule your bundle”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 127 testimonial or review blocks and a star rating.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Pinterest Tag and TikTok Pixel (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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 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.

  • 21 other companies contacted

    Loading the homepage contacts 21 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 abrismtl.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on abrismtl.ca, including 12 speed issues, 1 SEO issue 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