Website review, no card needed

goodr.ca logo

goodr.ca website review

Visit site (opens in a new tab)Reviewed 7 November 202633 issues · 85 checks

This review found 33 issues worth fixing on goodr.ca, 10 of them high impact, across 85 checks. The most urgent: render-blocking 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
651 ms480 msMay 16Oct 31631 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026596 ms
May 23, 2026573 ms
May 30, 2026558 ms
Jun 6, 2026548 ms
Jun 13, 2026547 ms
Jun 20, 2026558 ms
Jun 27, 2026564 ms
Jul 4, 2026562 ms
Jul 11, 2026564 ms
Jul 18, 2026563 ms
Jul 25, 2026563 ms
Aug 1, 2026574 ms
Aug 8, 2026577 ms
Aug 15, 2026589 ms
Aug 22, 2026610 ms
Aug 29, 2026616 ms
Sep 5, 2026611 ms
Sep 12, 2026596 ms
Sep 19, 2026565 ms
Sep 26, 2026538 ms
Oct 3, 2026512 ms
Oct 10, 2026500 ms
Oct 17, 2026557 ms
Oct 24, 2026592 ms
Oct 31, 2026631 ms
Real-visitor tap response (INP)75th percentile, phones
81 ms74 msMay 16Oct 3176 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202675 ms
May 23, 202675 ms
May 30, 202675 ms
Jun 6, 202677 ms
Jun 13, 202677 ms
Jun 20, 202678 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202679 ms
Jul 25, 202679 ms
Aug 1, 202678 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 12, 202680 ms
Sep 19, 202680 ms
Sep 26, 202680 ms
Oct 3, 202680 ms
Oct 10, 202678 ms
Oct 17, 202677 ms
Oct 24, 202677 ms
Oct 31, 202676 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 goodr.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. goodr.ca at 1.0 s1.0 s
  2. goodr.ca at 2.0 s2.0 s
  3. goodr.ca at 3.0 s3.0 s
  4. goodr.ca at 4.0 s4.0 s
  5. goodr.ca at 5.0 s5.0 s
  6. goodr.ca at 6.0 s6.0 s
  7. goodr.ca at 7.0 s7.0 s
  8. goodr.ca at 8.0 s8.0 s

Speed

8 to fix64
  • Render-blocking requests

    1.4 s

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

  • Main-thread work: 5.1 s

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

  • Mobile performance score: 64

    64/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Optanon, Yotpo and Accessibe Accessibility Overlay and others), adding 1.3 MB and 591 ms of main-thread time.

  • Reduce unused JavaScript

    604 KiB

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

  • Reduce unused CSS

    440 ms · 148 KiB

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

  • 4 long tasks on the main thread

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

  • 2,963 HTML elements

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

  • Use efficient cache lifetimes

    150 ms · 220 KiB

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

  • Improve image delivery

    150 ms · 202 KiB

    6 images could be 202 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.

  • Font display

    50 ms

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

  • Legacy JavaScript

    42 KiB

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 11.4 s

    11.4 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Total Blocking Time: 645 ms

    645 ms

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

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

    0.9 s

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

  • Real-user INP: 103 ms

    103 ms

    Real visitors wait 103 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: 333 ms

    333 ms

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

  • Cumulative Layout Shift: 0.053

    0.053

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

Images and page weight

2 to fix75
  • Page weight: 3.0 MB in 254 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 254 requests on a phone: scripts 1.3 MB (68), other files 721 KiB (105) and images 536 KiB (57). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    34 KiB

    1 image is downloaded at several times the size a phone draws it, for example placeholder.webp at 1,920 px wide, shown at 386 px. Resized copies would save about 34 KiB.

  • 3 images in older formats

    3 images (455 KiB) 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.

  • 1 image below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.86 g

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

Accessibility

7 to fixGoogle 8491
  • 1 button without a name

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

  • 6 text elements with low contrast

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

  • [role="img"] and [role="image"] elements must have alternative text (1 element)

    [role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • 7 images without alt text

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

  • Alternative text of images should not be repeated as text (37 elements)

    Alternative text of images should not be repeated as text: 37 elements on the page fail this check, rated minor by axe-core.

  • 3 links without text

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

  • Headings skip levels

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

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

2 to fixGoogle 7795
  • 16 links crawlers can't follow

    16 links have no real href, so search engines can't follow them.

  • 2 links with vague text

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

  • 420 internal links, 7 external

    The homepage links to 420 pages on goodr.ca and 7 external pages.

8 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “goodr Canada's affordable polarized sunglasses are no slip, no bounce, all polarized, and all fun. (AKA the best sungla…”.

  • One H1 headline

    Your main headline reads: “20% OFFSITEWIDE”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Sunglasses for Men & Women | goodr Canada”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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://goodr.ca/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.

3 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 (784 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://goodr.ca/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://goodr.ca/collections/slate-g has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://goodr.ca/collections/all-styles and https://goodr.ca/collections/the-ogs have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://goodr.ca/collections/the-ogs and https://goodr.ca/collections/lfgs took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 153 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

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://goodr.ca/.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “NotFoundError: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not …”.

  • 1 distorted image

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: 16 testimonial or review blocks. 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.

  • About 505 words of copy

    The homepage carries about 505 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “SHOP”, “Shop Now” and “SHOP NOW”.

  • 6 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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.

  • 9 cookies set on arrival

    9

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

  • 23 other companies contacted

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

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Onetrust Consent Management · Attentive · Yotpo Product Reviews · Klaviyo Email Marketing Sms · Hreflang Manager

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Hiring

Hiring
12 open roles
Teams
Retail Marketing (2), Don't see the right role? (1), Financial Planning & Analysis (1), Global (1)
Job board
greenhouse

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on goodr.ca, including 14 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