Website review, no card needed

lunapads.ca logo

lunapads.ca website review

Visit site (opens in a new tab)Reviewed 19 November 202642 issues · 87 checks

This review found 42 issues worth fixing on lunapads.ca, 13 of them high impact, across 87 checks. The most urgent: main-thread work: 40.2 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

Real-visitor load time (LCP)75th percentile, phones
1.7 s1.2 sMay 30Nov 141.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.7 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Nov 14, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
233 ms170 msMay 30Nov 14226 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026197 ms
Jun 6, 2026204 ms
Jun 13, 2026206 ms
Jun 20, 2026212 ms
Jun 27, 2026205 ms
Jul 4, 2026189 ms
Jul 11, 2026182 ms
Jul 18, 2026177 ms
Jul 25, 2026179 ms
Aug 1, 2026179 ms
Aug 8, 2026188 ms
Aug 15, 2026198 ms
Aug 22, 2026201 ms
Aug 29, 2026203 ms
Sep 5, 2026204 ms
Sep 12, 2026205 ms
Sep 19, 2026210 ms
Sep 26, 2026212 ms
Oct 3, 2026213 ms
Oct 10, 2026216 ms
Oct 17, 2026216 ms
Oct 24, 2026220 ms
Oct 31, 2026215 ms
Nov 7, 2026220 ms
Nov 14, 2026226 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 lunapads.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lunapads.ca at 2.6 s2.6 s
  2. lunapads.ca at 5.2 s5.2 s
  3. lunapads.ca at 7.8 s7.8 s
  4. lunapads.ca at 10.4 s10.4 s
  5. lunapads.ca at 13.1 s13.1 s
  6. lunapads.ca at 15.7 s15.7 s
  7. lunapads.ca at 18.3 s18.3 s
  8. lunapads.ca at 20.9 s20.9 s

Speed

12 to fix55
  • Main-thread work: 40.2 s

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

  • Clarity adds 1.3 s

    1.3 s

    Clarity costs a phone 1.3 s of main-thread work and 28 KiB 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.

  • 4,879 HTML elements

    The page has 4,879 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 (Clarity, Shopify and Klaviyo and others), adding 1.5 MB and 1.8 s of main-thread time.

  • Mobile performance score: 55

    55/100

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

  • Render-blocking requests

    950 ms

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

  • Improve image delivery

    450 ms · 340 KiB

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

  • Reduce unused JavaScript

    150 ms · 522 KiB

    About 522 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 126 KiB

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

  • Shopify adds 185 ms

    185 ms

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

  • Klaviyo adds 168 ms

    168 ms

    Klaviyo costs a phone 168 ms of main-thread work and 326 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.

  • azurefd.net adds 60 ms

    60 ms

    azurefd.net costs a phone 60 ms of main-thread work and 315 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

    100 ms · 225 KiB

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

  • 20 long tasks on the main thread

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

  • Minify CSS

    24 KiB

    24 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    19 KiB

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

  • Minify JavaScript

    14 KiB

    14 KiB could be saved by minifying JavaScript.

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

    18 ms

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

Core Web Vitals

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

  • Speed Index: 17.3 s

    17.3 s

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

  • Time to Interactive: 25.5 s

    25.5 s

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

  • Largest Contentful Paint: 9.0 s

    9.0 s

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

  • Real-user INP: 330 ms

    330 ms

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

  • Largest content (LCP) got 26% slower for real visitors

    +26%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Total Blocking Time: 361 ms

    361 ms

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

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

    +11%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • 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 TTFB: 444 ms

    444 ms

    Real visitors wait 444 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 fix75
  • Page weight: 3.5 MB in 301 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 301 requests on a phone: scripts 1.6 MB (193), images 1.0 MB (41) and fonts 417 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    26 KiB

    1 image is downloaded at several times the size a phone draws it, for example Aisle_SS26_C02_Studio-Greenery_49145_high_res.jpg at 1,350 px wide, shown at 390 px. Resized copies would save about 26 KiB.

  • 1 image in older formats

    1 image (85 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.

  • 1 image below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    1.00 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 119.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 8489
  • Hidden but focusable

    23 elements hidden from screen readers can still receive keyboard focus.

  • Elements must only use permitted ARIA attributes (7 elements)

    Elements must only use permitted ARIA attributes: 7 elements on the page fail this check, rated serious by axe-core.

  • 4 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 4 images without alt text

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

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

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

  • 40 links without text

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

  • Headings skip levels

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

1 checks passed
  • 50 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: 50 passed and 8 failed. 2 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
  • 7 H1 headlines

    There are 7 <h1> headlines (“Aisle”, “Shop New Arrivals” and “Compare Our Leakproof Systems”). One clear main headline is easier for people and search engines.

  • 222 internal links, 4 external

    The homepage links to 222 pages on lunapads.ca and 4 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Shop Aisle’s leakproof underwear for periods and bladder leaks, plus new prebiotic underwear with fabric that fosters g…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Aisle Leakproof & Prebiotic Undies | Nurture Your Nature™”.

  • Canonical URL set

    The canonical URL is https://periodaisle.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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://periodaisle.com/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.

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

  • llms.txt published

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

Other pages

4 to fix81
  • 2 pages share a title

    https://periodaisle.com/collections/all and https://periodaisle.com/collections/shop-all-leakproof all use the title “Shop All | Leakproof Period Underwear & Reusable Pads | Aisle”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://periodaisle.com/collections/best-seller, https://periodaisle.com/collections/kits, https://periodaisle.com/collections/boxers, https://periodaisle.com/collections/briefs, https://periodaisle.com/collections/hipsters and https://periodaisle.com/collections/bikinis and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://periodaisle.com/collections/all and https://periodaisle.com/collections/shop-all-leakproof use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://periodaisle.com/collections/all, https://periodaisle.com/collections/shop-all-leakproof and https://periodaisle.com/products/bralette have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://periodaisle.com/collections/all 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.

  • 15 internal pages checked

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

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=39280ac7-bd2d-42af-ae32-321876079283&referrer=&landingpage=https%3A%2F%2Fperiodaisle.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%201.

  • 9 small tap targets

    9 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • A 11-field form

    Your longest form asks for 11 fields (0 required). Every extra field lowers completion.

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

    The homepage carries about 463 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP LEAKPROOF UNDIES” and “SHOP PREBIOTIC UNDIES”.

  • 61 calls to action

    The homepage has 61 calls to action, for example “Shop All”, “Shop Prebiotic Undies” and “Shop Leakproof Undies”.

  • Social proof on the page

    Social proof on the homepage: 93 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

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, Klaviyo and Meta Pixel 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.

  • 26 cookies set on arrival

    26

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

  • 49 other companies contacted

    Loading the homepage contacts 49 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 lunapads.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 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Microsoft Clarity · Awin Affiliate Marketing · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Analyzify Ga4 Ads Tracking · Triplewhale · Videowise Connect · Event Promotion Bar · Bestpush · Booster Kit By Qikify · usecorner.io · cornercart.io · hextom.com · influencer-hero.com

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on lunapads.ca, including 21 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