Website review, no card needed

dilawri.ca logo

dilawri.ca website review

Visit site (opens in a new tab)Reviewed 31 October 202659 issues · 105 checks

This review found 59 issues worth fixing on dilawri.ca, 27 of them high impact, across 105 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
2.1 s1.9 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
426 ms235 msMay 9Oct 24404 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026271 ms
May 16, 2026271 ms
May 23, 2026261 ms
May 30, 2026257 ms
Jun 6, 2026260 ms
Jun 13, 2026261 ms
Jun 20, 2026262 ms
Jun 27, 2026269 ms
Jul 4, 2026274 ms
Jul 11, 2026281 ms
Jul 18, 2026294 ms
Jul 25, 2026304 ms
Aug 1, 2026303 ms
Aug 8, 2026310 ms
Aug 15, 2026321 ms
Aug 22, 2026321 ms
Aug 29, 2026348 ms
Sep 5, 2026349 ms
Sep 12, 2026346 ms
Sep 19, 2026356 ms
Sep 26, 2026352 ms
Oct 3, 2026362 ms
Oct 10, 2026379 ms
Oct 17, 2026395 ms
Oct 24, 2026404 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 dilawri.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dilawri.ca at 1.4 s1.4 s
  2. dilawri.ca at 2.9 s2.9 s
  3. dilawri.ca at 4.3 s4.3 s
  4. dilawri.ca at 5.7 s5.7 s
  5. dilawri.ca at 7.1 s7.1 s
  6. dilawri.ca at 8.6 s8.6 s
  7. dilawri.ca at 10.0 s10.0 s
  8. dilawri.ca at 11.4 s11.4 s

Speed

13 to fix25
  • Reduce unused JavaScript

    9.3 s · 3.5 MB

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

  • Render-blocking requests

    4.8 s

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

  • Use efficient cache lifetimes

    2.5 s · 1.1 MB

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

  • Google Tag Manager adds 3.2 s

    3.2 s

    Google Tag Manager costs a phone 3.2 s of main-thread work and 2.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 12.1 s

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

  • Mobile performance score: 25

    25/100

    Your mobile performance score is 25. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

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

  • Improve image delivery

    100 ms · 3.8 MB

    47 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Google CDN adds 870 ms

    870 ms

    Google CDN costs a phone 870 ms of main-thread work and 1.5 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.

  • sm360.ca adds 393 ms

    393 ms

    sm360.ca costs a phone 393 ms of main-thread work and 4.6 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.

  • Facebook adds 686 ms

    686 ms

    Facebook costs a phone 686 ms of main-thread work and 489 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.

  • 20 long tasks on the main thread

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

  • impel.io adds 250 ms

    250 ms

    impel.io costs a phone 250 ms of main-thread work and 480 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.

  • Reduce unused CSS

    160 ms · 117 KiB

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    30 KiB

    Polyfills for old browsers add 30 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.

  • Forced reflow

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

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

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

  • First Contentful Paint: 9.5 s

    9.5 s

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

  • Largest Contentful Paint: 24.0 s

    24.0 s

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

  • Speed Index: 17.2 s

    17.2 s

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

  • Time to Interactive: 60.5 s

    60.5 s

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

  • Total Blocking Time: 4.0 s

    4.0 s

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

  • Real-user INP: 271 ms

    271 ms

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

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

    +47%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 628 ms

    628 ms

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

  • Cumulative Layout Shift: 0.019

    0.019

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

Images and page weight

5 to fix18
  • Page weight: 12.8 MB in 310 requests

    12.8 MB

    Your homepage downloads 12.8 MB in 310 requests on a phone: scripts 7.3 MB (97), images 4.0 MB (85) and other files 972 KiB (95). Under 2 MB keeps phones on slow connections fast.

  • 19 images far larger than shown

    3.0 MB

    19 images are downloaded at several times the size a phone draws them, for example ram1742400935761.png at 800 px wide, shown at 80 px. Resized copies would save about 3.0 MB.

  • 1 image over 500 KB

    ram1742400935761.png weighs 900 KiB. On a phone connection a single image that size takes seconds.

  • 34 images below the first screen load straight away

    34 images further down the page (3.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 25 images in older formats

    25 images (3.5 MB) are 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.

  • About 3.6 g of CO₂ per visit

    3.62 g

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

Accessibility

21 to fixGoogle 5575
  • Required ARIA attributes must be provided (5 elements)

    Required ARIA attributes must be provided: 5 elements on the page fail this check, rated critical by axe-core.

  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

  • ARIA input fields must have an accessible name (2 elements)

    ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

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

  • Contentinfo landmark should not be contained in another landmark (2 elements)

    Contentinfo landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 7 form fields without a label

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements marked as presentational should be consistently ignored (3 elements)

    Elements marked as presentational should be consistently ignored: 3 elements on the page fail this check, rated minor by axe-core.

  • ARIA role should be appropriate for the element (2 elements)

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 9287
  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (207 characters)

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

  • Structured data has 3 problems

    Structured data found (WebSite) but with 3 problems, for example “WebSite: missing name”.

  • 120 internal links, 11 external

    The homepage links to 120 pages on dilawri.ca and 11 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Discover Our Family of Brands”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Dilawri | Canada’s Largest Automotive Group”.

  • 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.dilawri.ca/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.dilawri.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 (404 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.dilawri.ca/en/dilawri-leasing has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.dilawri.ca/en/inventory, https://www.dilawri.ca/en/shop-online and https://www.dilawri.ca/en/research 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 58 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 8891
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 265 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All” and “Shop New”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Shop”, “Shop All” and “Shop New”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 5 trackers load before any consent

    5

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

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 cookies, 1 of them by other companies (measured from a US location before any click).

  • 50 other companies contacted

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

1 checks passed
  • Consent tool: Didomi

    A consent management tool (Didomi) 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 dilawri.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 59 issues on dilawri.ca, including 21 speed issues, 3 SEO issues and 4 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