Website review, no card needed

lornashorestore.com logo

lornashorestore.com website review

Visit site (opens in a new tab)Reviewed 16 November 202635 issues · 82 checks

This review found 35 issues worth fixing on lornashorestore.com, 12 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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
939 ms793 msMay 30Nov 14810 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026839 ms
Jun 6, 2026846 ms
Jun 13, 2026851 ms
Jun 20, 2026865 ms
Jun 27, 2026849 ms
Jul 4, 2026829 ms
Jul 11, 2026829 ms
Jul 18, 2026830 ms
Jul 25, 2026853 ms
Aug 1, 2026874 ms
Aug 8, 2026884 ms
Aug 15, 2026894 ms
Aug 22, 2026898 ms
Aug 29, 2026908 ms
Sep 5, 2026917 ms
Sep 12, 2026922 ms
Sep 19, 2026922 ms
Sep 26, 2026922 ms
Oct 3, 2026913 ms
Oct 10, 2026893 ms
Oct 17, 2026889 ms
Oct 24, 2026871 ms
Oct 31, 2026854 ms
Nov 7, 2026837 ms
Nov 14, 2026810 ms
Real-visitor tap response (INP)75th percentile, phones
143 ms107 msMay 30Nov 14124 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026111 ms
Jun 6, 2026112 ms
Jun 13, 2026113 ms
Jun 20, 2026117 ms
Jun 27, 2026114 ms
Jul 4, 2026114 ms
Jul 11, 2026113 ms
Jul 18, 2026113 ms
Jul 25, 2026114 ms
Aug 1, 2026116 ms
Aug 8, 2026120 ms
Aug 15, 2026121 ms
Aug 22, 2026126 ms
Aug 29, 2026129 ms
Sep 5, 2026130 ms
Sep 12, 2026132 ms
Sep 19, 2026133 ms
Sep 26, 2026136 ms
Oct 3, 2026137 ms
Oct 10, 2026138 ms
Oct 17, 2026139 ms
Oct 24, 2026138 ms
Oct 31, 2026136 ms
Nov 7, 2026130 ms
Nov 14, 2026124 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 lornashorestore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lornashorestore.com at 0.5 s0.5 s
  2. lornashorestore.com at 1.0 s1.0 s
  3. lornashorestore.com at 1.5 s1.5 s
  4. lornashorestore.com at 1.9 s1.9 s
  5. lornashorestore.com at 2.4 s2.4 s
  6. lornashorestore.com at 2.9 s2.9 s
  7. lornashorestore.com at 3.4 s3.4 s
  8. lornashorestore.com at 3.9 s3.9 s

Speed

11 to fix58
  • Use efficient cache lifetimes

    2.5 s · 352 KiB

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

  • Reduce unused JavaScript

    1.5 s · 266 KiB

    About 266 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • 3,234 HTML elements

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

  • Mobile performance score: 58

    58/100

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

  • Render-blocking requests

    750 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Shopify and avada.io and others), adding 1.1 MB and 533 ms of main-thread time.

  • Facebook adds 322 ms

    322 ms

    Facebook costs a phone 322 ms of main-thread work and 327 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

    300 ms · 35 KiB

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

  • Improve image delivery

    314 KiB

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

  • Main-thread work: 2.1 s

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

  • Shopify adds 102 ms

    102 ms

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

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    11 KiB

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

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 16.6 s

    16.6 s

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

  • Time to Interactive: 17.1 s

    17.1 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Speed Index: 8.8 s

    8.8 s

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

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

    +14%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

8 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: 162 ms

    162 ms

    Real visitors wait 162 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: 353 ms

    353 ms

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

  • Total Blocking Time: 104 ms

    104 ms

    Scripts block the page for only 104 ms while loading. Good is under 200 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 fix83
  • Page weight: 4.0 MB in 199 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 199 requests on a phone: images 2.2 MB (35), scripts 999 KiB (66) and other files 665 KiB (79). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    tee-in-darkness-6.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.13 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9194
  • Scrollable region must have keyboard access (12 elements)

    Scrollable region must have keyboard access: 12 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 6 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → 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 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9283
  • Title is short (11 characters)

    Your title is only 11 characters: “Lorna Shore”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (26 characters)

    Your meta description is only 26 characters: “Lorna Shore Official Store”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Lorna Shore Lorna Shore” and “Lorna Shore Official Photo Book”). One clear main headline is easier for people and search engines.

  • 250 internal links, 25 external

    The homepage links to 250 pages on lornashorestore.com and 25 external pages.

5 checks passed
  • Canonical URL set

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

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://lornashoreband.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://lornashoreband.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 pages without a meta description

    https://lornashoreband.com/pages/tour, https://lornashoreband.com/customer_authentication/redirect, https://lornashoreband.com/collections/summer-2026-tour-merch, https://lornashoreband.com/collections/war-machine, https://lornashoreband.com/collections/summer-2026 and https://lornashoreband.com/collections/spring-2026-tour-merch and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://lornashoreband.com/customer_authentication/redirect has 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 131 found) and read each the way a search engine does.

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

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 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 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 2,821 words of copy

    The homepage carries about 2,821 words of visible text.

4 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Shop”, “Shop Intl” and “Shop IntlShop Intl”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Meta Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.

  • 11 cookies set on arrival

    11

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 lornashorestore.com, 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

Tnc Terms Checkbox · Shopify Cli · Selleasy · Avada Order Limit · herokuapp.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

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

Company

Founded
2010

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on lornashorestore.com, including 15 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