Website review, no card needed

ottawajadran.ca logo

ottawajadran.ca website review

Visit site (opens in a new tab)Reviewed 13 November 202618 issues · 66 checks

This review found 18 issues worth fixing on ottawajadran.ca, 4 of them high impact, across 66 checks. The most urgent: aRIA commands must have an accessible name (5 elements). 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 ottawajadran.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ottawajadran.ca at 0.6 s0.6 s
  2. ottawajadran.ca at 1.3 s1.3 s
  3. ottawajadran.ca at 1.9 s1.9 s
  4. ottawajadran.ca at 2.6 s2.6 s
  5. ottawajadran.ca at 3.2 s3.2 s
  6. ottawajadran.ca at 3.9 s3.9 s
  7. ottawajadran.ca at 4.5 s4.5 s
  8. ottawajadran.ca at 5.2 s5.2 s

Speed

4 to fix71
  • Mobile performance score: 71

    71/100

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

  • Improve image delivery

    362 KiB

    19 images could be 362 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Shopify adds 34 ms

    34 ms

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

  • openstreetmap.org adds 0 ms

    0 ms

    openstreetmap.org costs a phone 0 ms of main-thread work and 561 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.

  • Use efficient cache lifetimes

    226 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Unpkg, Shopify and Google Fonts and others), adding 966 KiB and 75 ms of main-thread time.

  • Render-blocking requests

    150 ms

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

  • 2 long tasks on the main thread

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

  • Reduce unused JavaScript

    24 KiB

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

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

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix69
  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “★ HOSTED BY JADRAN OTTAWA ★ HNNS TURNIR 62 Igraj. Slavi. Pa…”.

  • Time to Interactive: 7.0 s

    7.0 s

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

  • Speed Index: 4.8 s

    4.8 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 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
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 36 ms

    36 ms

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

Images and page weight

100
  • 9 images below the first screen load straight away

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

  • 4 images in older formats

    4 images (140 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.

  • About 0.5 g of CO₂ per visit

    0.54 g

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

2 checks passed
  • Page weight: 1.9 MB in 161 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 161 requests on a phone: images 841 KiB (20), other files 731 KiB (81) and scripts 235 KiB (43). That is a lean page.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9395
  • ARIA commands must have an accessible name (5 elements)

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 40 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: 40 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9278
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (13 characters)

    Your title is only 13 characters: “JADRAN OTTAWA”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “HNNS TURNIR 62”). One clear main headline is easier for people and search engines.

  • 5 internal links, 0 external

    The homepage links to 5 pages on ottawajadran.ca and 0 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://ottawajadran.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://ottawajadran.ca/sitemap.xml.

AI search readiness

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 2 pages without a meta description

    https://ottawajadran.ca/pages/shop-turnir-62 and https://ottawajadran.ca/pages/hotel-reservations have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://ottawajadran.ca/pages/shop-turnir-62 has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 2 internal pages checked

    We fetched 2 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 2 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 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 2 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

  • Only about 231 words

    The homepage has only about 231 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “MERCH SHOP TURNIR 62 →”.

  • 1 call to action

    The homepage has 1 call to action, for example “Merch Shop Turnir 62 →”.

  • 3 short forms

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

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 9 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Apps on your store

No apps were seen in the code your storefront loads.

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on ottawajadran.ca, including 8 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