Website review, no card needed

getpurpledot.com logo

getpurpledot.com website review

Visit site (opens in a new tab)Reviewed 6 November 202623 issues · 74 checks

This review found 23 issues worth fixing on getpurpledot.com, 3 of them high impact, across 74 checks. The most urgent: 2 pages without a title. 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.6 s625 msMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026895 ms
May 23, 2026899 ms
May 30, 2026894 ms
Jun 6, 2026868 ms
Jun 13, 2026893 ms
Jun 20, 2026906 ms
Jun 27, 2026957 ms
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 20262.1 s
Jul 25, 20262.2 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20261.9 s
Sep 5, 20261.5 s
Sep 12, 20261.3 s
Sep 19, 20261.0 s
Sep 26, 2026978 ms
Oct 3, 2026849 ms
Oct 10, 2026910 ms
Oct 17, 2026980 ms
Oct 24, 20261.0 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
138 ms61 msMay 16Oct 3170 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202686 ms
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202677 ms
Jun 13, 202677 ms
Jun 20, 202671 ms
Jun 27, 202674 ms
Jul 4, 202674 ms
Jul 11, 202674 ms
Jul 18, 2026107 ms
Jul 25, 2026114 ms
Aug 1, 2026123 ms
Aug 8, 2026129 ms
Aug 15, 2026124 ms
Aug 22, 2026124 ms
Aug 29, 2026119 ms
Sep 5, 2026108 ms
Sep 12, 2026105 ms
Sep 19, 202697 ms
Sep 26, 202693 ms
Oct 3, 202682 ms
Oct 10, 202679 ms
Oct 17, 202673 ms
Oct 24, 202670 ms
Oct 31, 202670 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 getpurpledot.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. getpurpledot.com at 0.5 s0.5 s
  2. getpurpledot.com at 0.9 s0.9 s
  3. getpurpledot.com at 1.4 s1.4 s
  4. getpurpledot.com at 1.8 s1.8 s
  5. getpurpledot.com at 2.3 s2.3 s
  6. getpurpledot.com at 2.7 s2.7 s
  7. getpurpledot.com at 3.2 s3.2 s
  8. getpurpledot.com at 3.6 s3.6 s

Speed

5 to fix94
  • Render-blocking requests

    900 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, website-files.com and FullStory and others), adding 1.7 MB and 704 ms of main-thread time.

  • Google Tag Manager adds 408 ms

    408 ms

    Google Tag Manager costs a phone 408 ms of main-thread work and 672 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 JavaScript

    424 KiB

    About 424 KiB of JavaScript is downloaded but never used on this page.

  • website-files.com adds 153 ms

    153 ms

    website-files.com costs a phone 153 ms of main-thread work and 873 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.

  • Improve image delivery

    204 KiB

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

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 19 KiB

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

  • Use efficient cache lifetimes

    131 KiB

    14 files are served with short cache lifetimes, so returning visitors download them again (131 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

3 checks passed
  • Mobile performance score: 94

    94/100

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

  • Main-thread work: 1.5 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 10.3 s

    10.3 s

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

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

  • Speed Index: 3.5 s

    3.5 s

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

  • 4 images without width and height

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

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

    +18%

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

10 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.1 s

    1.1 s

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

  • Real-user INP: 81 ms

    81 ms

    Real visitors wait 81 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: 284 ms

    284 ms

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

  • Tap response (INP) got 15% faster for real visitors

    -15%

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

  • Total Blocking Time: 156 ms

    156 ms

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

  • Cumulative Layout Shift: 0.036

    0.036

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

Images and page weight

100
  • 1 image in older formats

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

    0.51 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 61.0 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: 1.8 MB in 96 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 96 requests on a phone: scripts 1.0 MB (24), images 613 KiB (33) and fonts 91 KiB (3). 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

3 to fixGoogle 9695
  • 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.

  • 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 50 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

5 to fixGoogle 10075
  • Title is short (4 characters)

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

  • 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 short (28 characters)

    Your meta description is only 28 characters: “Pre-orders That Power Growth”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Pre-orders That Power Growth” and “Ready to learn more?”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 42 internal links, 6 external

    The homepage links to 42 pages on getpurpledot.com and 6 external pages.

3 checks passed
  • 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://www.getpurpledot.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.

  • No llms.txt

    There is no https://www.getpurpledot.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

Other pages

3 to fix75
  • 2 pages without a title

    https://www.getpurpledot.com/case-studies/how-astrid-miyu-used-pre-order-automation-to-maximize-sales-and-save-time and https://www.getpurpledot.com/case-studies/how-tonies-uses-pre-orders-to-launch-early-and-sell-more have no <title>, so Google invents the link text in results.

  • 3 pages without a meta description

    https://www.getpurpledot.com/book-a-demo, https://www.getpurpledot.com/case-studies/how-astrid-miyu-used-pre-order-automation-to-maximize-sales-and-save-time and https://www.getpurpledot.com/case-studies/how-tonies-uses-pre-orders-to-launch-early-and-sell-more have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.getpurpledot.com/why-purple-dot and https://www.getpurpledot.com/why-pre-orders 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 25 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.

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

Best practices

Google 100100
2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: 28 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • About 679 words of copy

    The homepage carries about 679 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a demo”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Book a demo” and “Find your pre-order”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • 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
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight (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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 1 of them by other companies (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.

  • 25 other companies contacted

    Loading the homepage contacts 25 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 getpurpledot.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Analytics | Google Tag Manager | FullStory
Hosting
Webflow

Company

Headquarters
London

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on getpurpledot.com, including 9 speed issues, 5 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