Website review, no card needed

ayoubs.ca logo

ayoubs.ca website review

Visit site (opens in a new tab)Reviewed 8 November 202634 issues · 81 checks

This review found 34 issues worth fixing on ayoubs.ca, 11 of them high impact, across 81 checks. The most urgent: page weight: 12.8 MB in 505 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.2 s1.9 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
237 ms142 msMay 16Oct 31221 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026153 ms
May 23, 2026163 ms
May 30, 2026167 ms
Jun 6, 2026170 ms
Jun 13, 2026171 ms
Jun 20, 2026170 ms
Jun 27, 2026173 ms
Jul 4, 2026177 ms
Jul 11, 2026178 ms
Jul 18, 2026170 ms
Jul 25, 2026166 ms
Aug 1, 2026162 ms
Aug 8, 2026170 ms
Aug 15, 2026173 ms
Aug 22, 2026174 ms
Aug 29, 2026181 ms
Sep 5, 2026178 ms
Sep 12, 2026181 ms
Sep 19, 2026195 ms
Sep 26, 2026204 ms
Oct 3, 2026220 ms
Oct 10, 2026222 ms
Oct 17, 2026226 ms
Oct 24, 2026221 ms
Oct 31, 2026221 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 ayoubs.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ayoubs.ca at 0.7 s0.7 s
  2. ayoubs.ca at 1.4 s1.4 s
  3. ayoubs.ca at 2.1 s2.1 s
  4. ayoubs.ca at 2.8 s2.8 s
  5. ayoubs.ca at 3.5 s3.5 s
  6. ayoubs.ca at 4.2 s4.2 s
  7. ayoubs.ca at 4.9 s4.9 s
  8. ayoubs.ca at 5.6 s5.6 s

Speed

8 to fix
  • Main-thread work: 9.3 s

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

  • 3,168 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hotjar and Yotpo and others), adding 7.5 MB and 2.2 s of main-thread time.

  • Google Tag Manager adds 549 ms

    549 ms

    Google Tag Manager costs a phone 549 ms of main-thread work and 844 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.

  • Yotpo adds 340 ms

    340 ms

    Yotpo costs a phone 340 ms of main-thread work and 581 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.

  • Hotjar adds 354 ms

    354 ms

    Hotjar costs a phone 354 ms of main-thread work and 65 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.

  • rebuyengine.com adds 231 ms

    231 ms

    rebuyengine.com costs a phone 231 ms of main-thread work and 857 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.

  • PayPal adds 206 ms

    206 ms

    PayPal costs a phone 206 ms of main-thread work and 392 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.

  • Font display

    50 ms

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

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

    17 ms

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

Core Web Vitals

4 to fix100
  • Speed Index: 13.6 s

    13.6 s

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

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

    +40%

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 14 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.0 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: 1.2 s

    1.2 s

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

  • Real-user INP: 195 ms

    195 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 372 ms

    372 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 12.8 MB in 505 requests

    12.8 MB

    Your homepage downloads 12.8 MB in 505 requests on a phone: scripts 6.4 MB (162), other files 3.4 MB (246) and images 2.3 MB (52). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    339 KiB

    2 images are downloaded at several times the size a phone draws them, for example GIFTS_1200x1200_ff52ac48-2bd4-4182-bd68-6a261a229228.png at 1,200 px wide, shown at 63 px. Resized copies would save about 339 KiB.

  • 1 image in older formats

    1 image (94 KiB) 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.

  • About 3.6 g of CO₂ per visit

    3.63 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

8 to fixGoogle 8688
  • 17 text elements with low contrast

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails 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.

  • 7 images without alt text

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

  • 1 button without a name

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

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

  • 2 links without text

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

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

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

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 8576
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Ayoub's Dried Fruits & Nuts - Buy Daily Roasted Nuts & Fruits Online”.

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

  • 3 links with vague text

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

  • 179 internal links, 8 external

    The homepage links to 179 pages on ayoubs.ca and 8 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Product.

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

  • llms.txt published

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

Other pages

3 to fix85
  • 10 pages without a meta description

    https://ayoubs.ca/pages/gifts-tab, https://ayoubs.ca/collections/back-to-school, https://ayoubs.ca/collections/new-arrivals, https://ayoubs.ca/collections/best-sellers, https://ayoubs.ca/collections/organic-options and https://ayoubs.ca/collections/organic-nuts-seeds and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://ayoubs.ca/pages/subscription, whose canonical is https://ayoubs.ca/pages/contact. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://ayoubs.ca/collections/gifts, https://ayoubs.ca/pages/gifts-tab, https://ayoubs.ca/collections/back-to-school, https://ayoubs.ca/collections/best-sellers, https://ayoubs.ca/collections/nuts and https://ayoubs.ca/collections/roasted-nuts have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://ayoubs.ca/collections/gifts, https://ayoubs.ca/collections/back-to-school, https://ayoubs.ca/collections/best-sellers, https://ayoubs.ca/collections/nuts and https://ayoubs.ca/collections/roasted-nuts have 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.

  • 4 pages slow to respond

    https://ayoubs.ca/collections/organic-options, https://ayoubs.ca/collections/organic-nuts-seeds, https://ayoubs.ca/collections/organic-seeds and https://ayoubs.ca/collections/raw-nuts took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 5088
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

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

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage carries about 735 words of visible text.

6 checks passed
  • Clear next step on the first screen

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

  • 3 calls to action

    The homepage has 3 calls to action, for example “SHOP NOW”, “Contact Us” and “Buy a Franchise”.

  • 11 short forms

    11 short forms (3 fields at most) are right on the homepage.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and PostHog.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 32 cookies set on arrival

    32

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

  • 62 other companies contacted

    Loading the homepage contacts 62 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 ayoubs.ca, 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 34 issues on ayoubs.ca, including 12 speed issues and 4 SEO issues. 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