Website review, no card needed

therisingtide.com logo

therisingtide.com website review

Visit site (opens in a new tab)Reviewed 10 November 202618 issues · 71 checks

This review found 18 issues worth fixing on therisingtide.com, 2 of them high impact, across 71 checks. The most urgent: 6 text elements with low contrast. 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
977 ms867 msMay 23Nov 7911 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026964 ms
May 30, 2026954 ms
Jun 6, 2026951 ms
Jun 13, 2026927 ms
Jun 20, 2026924 ms
Jun 27, 2026917 ms
Jul 4, 2026930 ms
Jul 11, 2026946 ms
Jul 18, 2026925 ms
Jul 25, 2026911 ms
Aug 1, 2026898 ms
Aug 8, 2026880 ms
Aug 15, 2026892 ms
Aug 22, 2026904 ms
Aug 29, 2026903 ms
Sep 5, 2026919 ms
Sep 12, 2026925 ms
Sep 19, 2026929 ms
Sep 26, 2026957 ms
Oct 3, 2026954 ms
Oct 10, 2026959 ms
Oct 17, 2026956 ms
Oct 24, 2026925 ms
Oct 31, 2026914 ms
Nov 7, 2026911 ms
Real-visitor tap response (INP)75th percentile, phones
89 ms79 msMay 23Nov 788 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202680 ms
May 30, 202683 ms
Jun 6, 202684 ms
Jun 13, 202683 ms
Jun 20, 202682 ms
Jun 27, 202680 ms
Jul 4, 202680 ms
Jul 11, 202680 ms
Jul 18, 202681 ms
Jul 25, 202681 ms
Aug 1, 202680 ms
Aug 8, 202681 ms
Aug 15, 202681 ms
Aug 22, 202681 ms
Aug 29, 202681 ms
Sep 5, 202681 ms
Sep 12, 202681 ms
Sep 19, 202683 ms
Sep 26, 202684 ms
Oct 3, 202687 ms
Oct 10, 202687 ms
Oct 17, 202687 ms
Oct 24, 202688 ms
Oct 31, 202688 ms
Nov 7, 202688 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 therisingtide.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

1 to fix72
  • Mobile performance score: 72

    72/100

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Clarity, Shopify and Google CDN), adding 121 KiB and 272 ms of main-thread time.

  • 8 long tasks on the main thread

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

  • Use efficient cache lifetimes

    150 ms · 11 KiB

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

  • Render-blocking requests

    100 ms

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

  • Improve image delivery

    50 ms · 43 KiB

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

  • Reduce unused JavaScript

    67 KiB

    About 67 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.9 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “An image of a buffalo brown chesterfield leather chair in t…”.

  • Speed Index: 5.2 s

    5.2 s

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

  • Time to Interactive: 5.3 s

    5.3 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

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

    0.8 s

    Real visitors wait 0.8 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 FCP: 0.7 s

    0.7 s

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

  • Total Blocking Time: 182 ms

    182 ms

    Scripts block the page for only 182 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

100
  • 1 image in older formats

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

    0.12 g

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

3 checks passed
  • Page weight: 429 KiB in 78 requests

    429 KiB

    Your homepage downloads 429 KiB in 78 requests on a phone: scripts 189 KiB (35), images 138 KiB (8) and stylesheets 50 KiB (20). That is a lean page.

  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 9798
  • 6 text elements with low contrast

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 10087
  • Meta description is long (278 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 59 internal links, 15 external

    The homepage links to 59 pages on therisingtide.com and 15 external pages.

5 checks passed
  • Title: 49 characters

    Your title is a healthy 49 characters: “Rising Tide Design Co. | Home Goods & Furnishings”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

  • llms.txt published

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

Other pages

5 to fix76
  • 2 pages share a title

    https://therisingtide.com/pages/the-rising-tide-story and https://therisingtide.com/pages/our-story-1 all use the title “The Rising Tide Story – Rising Tide Design Co”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://therisingtide.com/policies/refund-policy, https://therisingtide.com/pages/customer-reviews, https://therisingtide.com/policies/privacy-policy, https://therisingtide.com/policies/terms-of-service and https://therisingtide.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://therisingtide.com/pages/the-rising-tide-story and https://therisingtide.com/pages/our-story-1 use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://therisingtide.com/pages/our-story-1, whose canonical is https://therisingtide.com/pages/the-rising-tide-story. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://therisingtide.com/pages/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 internal pages checked

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

3 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9697
  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 332 words of copy

    The homepage carries about 332 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 Chesterfield” and “Shop Aviator”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Contact Us”, “Shop Chesterfield” and “Shop Aviator”.

  • 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: 1 testimonial or review block and 1 customer or partner logo.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Microsoft Clarity (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.

  • 10 cookies set on arrival

    10

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

  • 7 other companies contacted

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

Apps your storefront loads

Simprosys Google Shopping Feed · Microsoft Clarity · loox.io

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
jQuery
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 18 issues on therisingtide.com, including 6 speed issues, 3 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