Website review, no card needed

harborthorne.com logo

harborthorne.com website review

Visit site (opens in a new tab)Reviewed 6 November 202618 issues · 94 checks

This review found 18 issues worth fixing on harborthorne.com, 0 of them high impact, across 94 checks. 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
2.1 s750 msMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026985 ms
May 23, 2026957 ms
May 30, 2026924 ms
Jun 6, 2026926 ms
Jun 13, 2026903 ms
Jun 20, 2026936 ms
Jun 27, 2026968 ms
Jul 4, 2026991 ms
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 2026964 ms
Aug 8, 2026966 ms
Aug 15, 2026960 ms
Aug 22, 2026956 ms
Aug 29, 2026995 ms
Sep 5, 20261.0 s
Sep 12, 2026983 ms
Sep 19, 20261.1 s
Sep 26, 20261.3 s
Oct 3, 20261.6 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20261.7 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
211 ms74 msMay 16Oct 31194 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202693 ms
May 23, 202690 ms
May 30, 202695 ms
Jun 6, 202696 ms
Jun 13, 202696 ms
Jun 20, 2026100 ms
Jun 27, 2026100 ms
Jul 4, 2026104 ms
Jul 11, 2026104 ms
Jul 18, 2026102 ms
Jul 25, 2026104 ms
Aug 1, 2026100 ms
Aug 8, 2026103 ms
Aug 15, 2026104 ms
Aug 22, 2026105 ms
Aug 29, 2026112 ms
Sep 5, 2026117 ms
Sep 12, 2026129 ms
Sep 19, 2026152 ms
Sep 26, 2026164 ms
Oct 3, 2026176 ms
Oct 10, 2026185 ms
Oct 17, 2026187 ms
Oct 24, 2026195 ms
Oct 31, 2026194 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 harborthorne.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. harborthorne.com at 0.4 s0.4 s
  2. harborthorne.com at 0.8 s0.8 s
  3. harborthorne.com at 1.1 s1.1 s
  4. harborthorne.com at 1.5 s1.5 s
  5. harborthorne.com at 1.9 s1.9 s
  6. harborthorne.com at 2.3 s2.3 s
  7. harborthorne.com at 2.6 s2.6 s
  8. harborthorne.com at 3.0 s3.0 s

harborthorne.com does not allow embedding, so this is Google's rendering of the page.

Speed

3 to fix100
  • Improve image delivery

    883 KiB

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

  • Render-blocking requests

    750 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

  • 1,646 HTML elements

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, pagepilot.ai and cloudfront.net and others), adding 615 KiB and 15 ms of main-thread time.

  • Reduce unused CSS

    41 KiB

    About 41 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    11 KiB

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

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

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

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

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

2 to fix100
  • Tap response (INP) got 113% slower for real visitors

    +113%

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

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

    +65%

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

12 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.8 s

    1.8 s

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

  • Real-user INP: 161 ms

    161 ms

    Real visitors wait 161 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: 1.0 s

    1.0 s

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

  • Real-user TTFB: 609 ms

    609 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.004

    0.004

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Speed Index: 1.6 s

    1.6 s

    Visually, the page fills in at 1.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.2 s

    1.2 s

    The page is fully interactive after 1.2 s.

Images and page weight

2 to fix75
  • Page weight: 2.3 MB in 70 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 70 requests on a phone: images 1.3 MB (32), scripts 739 KiB (28) and HTML 81 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    243 KiB

    4 images are downloaded at several times the size a phone draws them, for example download-2025-05-29T013240.353.png at 800 px wide, shown at 195 px. Resized copies would save about 243 KiB.

  • 1 image in older formats

    1 image (116 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 0.6 g of CO₂ per visit

    0.64 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 77.3 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

2 to fixGoogle 9698
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (180 characters)

    Your meta description is 180 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 203 internal links, 2 external

    The homepage links to 203 pages on harborthorne.com and 2 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Harbor & Thorne”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Harbor & Thorne | Home Essentials, Decor, Apparel & More”.

  • Canonical URL set

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

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

  • llms.txt published

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

Other pages

2 to fix90
  • 15 pages without a meta description

    /collections/mens-apparel, /collections/t-shirts, /collections/polo-shirts, /collections/button-ups, /collections/sweaters and /collections/hoodies and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    /collections/mens-apparel, /collections/t-shirts, /collections/polo-shirts, /collections/button-ups, /collections/sweaters and /collections/hoodies and 9 others have 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 104 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

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (harborthorne.com).

  • Valid certificate (68 days left)

    The certificate from Let's Encrypt · YE1 verifies for harborthorne.com and is valid for another 68 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://harborthorne.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 42 links work

    All 42 links checked from your homepage (40 internal, 2 external) answered without errors.

Domain and trust

  • No CAA record

    harborthorne.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    harborthorne.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 2 years old

    2 years

    harborthorne.com was registered in Aug 2024 through NameCheap, Inc.. An established domain carries more trust with email providers and search engines.

  • Registered until Aug 2027

    harborthorne.com is registered until Aug 2027.

Content and conversion

1 to fix94
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 446 words of visible text.

7 checks passed
  • Clear next step on the first screen

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

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact”, “Shop Women” and “Shop Men”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks, a star rating and “120,000+ Happy Customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Email authentication

2 to fix60
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be harborthorne.com is still delivered. Add a report address, check the reports, then move to quarantine.

  • No DKIM key on the usual selectors

    We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

  • Email authentication score: 60/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

1 checks passed
  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:mailgun.org ~all”.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

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

  • 5 other companies contacted

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

Apps on your store

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

  • Selleasy · problem reported Oct 2026attackers planted code in its settings that sent shoppers who pressed Checkout to a fake checkout page taking card details. What to do: update the app, check its settings for code or HTML you didn't add, and test checkout in a private window.

Your store uses an app that was used in an attack. That is not a sign you were hit: check the app as described.

Apps your storefront loads

Judge Me Reviews · Pixee Facebook Pixel · Bucks · Awin Affiliate Marketing · Uppromote Affiliate · Triplewhale · Kaching Bundles · Simprosys Google Shopping Feed · Microsoft Clarity · Selleasy · Affliate By Secomapp · Omnisend · Applovin Shop Integration · Aftersell · Upcart · gropulse.com · postscript.io · cloudfront.net

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 Analytics | Google Tag Manager | 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 18 issues on harborthorne.com, including 5 speed issues, 2 SEO issues and 1 conversion gap. 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