Programmable

Website review, no card needed

tellculvers.com logo

tellculvers.com website review

Visit site (opens in a new tab)Reviewed 11 October 202624 issues · 63 checks

This review found 24 issues worth fixing on tellculvers.com, 6 of them high impact, across 63 checks. The most urgent: render-blocking requests. 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

Site score

84B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
967 ms484 msApr 18Oct 3576 ms
Show as table
DateReal-visitor load time (LCP)
Apr 18, 2026576 ms
Apr 25, 2026580 ms
May 2, 2026578 ms
May 9, 2026614 ms
May 16, 2026653 ms
May 23, 2026723 ms
May 30, 2026845 ms
Jun 6, 2026911 ms
Jun 13, 2026808 ms
Jun 20, 2026697 ms
Jun 27, 2026625 ms
Jul 4, 2026540 ms
Jul 11, 2026549 ms
Jul 18, 2026564 ms
Jul 25, 2026580 ms
Aug 1, 2026602 ms
Aug 8, 2026631 ms
Aug 15, 2026670 ms
Aug 22, 2026689 ms
Aug 29, 2026691 ms
Sep 5, 2026668 ms
Sep 12, 2026624 ms
Sep 19, 2026601 ms
Sep 26, 2026589 ms
Oct 3, 2026576 ms
Real-visitor tap response (INP)75th percentile, phones
58 ms55 msApr 18Oct 355 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202658 ms
Apr 25, 202658 ms
May 2, 202658 ms
May 9, 202658 ms
May 16, 202658 ms
May 23, 202658 ms
May 30, 202657 ms
Jun 6, 202656 ms
Jun 13, 202656 ms
Jun 20, 202655 ms
Jun 27, 202656 ms
Jul 4, 202656 ms
Jul 11, 202655 ms
Jul 18, 202656 ms
Jul 25, 202655 ms
Aug 1, 202655 ms
Aug 8, 202655 ms
Aug 15, 202655 ms
Aug 22, 202655 ms
Aug 29, 202655 ms
Sep 5, 202655 ms
Sep 12, 202655 ms
Sep 19, 202655 ms
Sep 26, 202655 ms
Oct 3, 202655 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

tellculvers.com (opens in a new tab)
Full-page screenshot of tellculvers.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tellculvers.com at 0.4 s0.4 s
  2. tellculvers.com at 0.8 s0.8 s
  3. tellculvers.com at 1.2 s1.2 s
  4. tellculvers.com at 1.6 s1.6 s
  5. tellculvers.com at 2.0 s2.0 s
  6. tellculvers.com at 2.4 s2.4 s
  7. tellculvers.com at 2.8 s2.8 s
  8. tellculvers.com at 3.2 s3.2 s

Speed

3 to fix93

  • Render-blocking requests

    1.4 s

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Use efficient cache lifetimes

    1.0 s · 154 KiB

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

  • Reduce unused JavaScript

    330 ms · 56 KiB

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

  • Minify JavaScript

    150 ms · 6 KiB

    6 KiB could be saved by minifying JavaScript.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 76 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    7 KiB

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

3 checks passed

  • Mobile performance score: 93

    93/100

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

  • Main-thread work: 0.3 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

3 to fix100

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

  • Speed Index: 4.1 s

    4.1 s

    Visually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 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

    -5%

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

  • Largest content (LCP) held steady for real visitors

    +1%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 0.6 s to 0.6 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: 0.6 s

    0.6 s

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

  • Real-user INP: 56 ms

    56 ms

    Real visitors wait 56 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.6 s

    0.6 s

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

  • Real-user TTFB: 407 ms

    407 ms

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

  • Largest Contentful Paint: 2.5 s

    2.5 s

    Your largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “The 15 character survey code can be found near the bottom o…”.

  • Time to Interactive: 2.5 s

    2.5 s

    The page is fully interactive after 2.5 s.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 26 ms

    26 ms

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

Images and page weight

100

  • About 0.04 g of CO₂ per visit

    0.04 g

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

4 checks passed

  • Page weight: 159 KiB in 20 requests

    159 KiB

    Your homepage downloads 159 KiB in 20 requests on a phone: scripts 117 KiB (10), images 20 KiB (5) and stylesheets 19 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

2 checks passed

  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

7 to fixGoogle 9268

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Culver's Guest Satisfaction Survey - Welcome”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://tellculvers.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at tellculvers.com/robots.txt, the first file search crawlers ask for.

  • Only 1 internal link

    The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

2 checks passed

  • Title: 44 characters

    Your title is a healthy 44 characters: “Culver's Guest Satisfaction Survey - Welcome”.

  • Canonical URL set

    The canonical URL is http://tellculvers.com/Index.aspx.

AI search readiness

1 to fix83

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

1 checks passed

  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Best practices

2 to fixGoogle 9267

  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 4 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed

  • No console errors

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

Content and conversion

5 to fix50

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 100 words

    The homepage has only about 100 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed

  • 1 call to action

    The homepage has 1 call to action, for example “Start”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • 5 cookies set on arrival

    5

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on tellculvers.com, including 6 speed issues, 7 SEO issues and 5 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