Website review, no card needed

guthy-renker.com logo

guthy-renker.com website review

Visit site (opens in a new tab)Reviewed 3 November 202640 issues · 80 checks

This review found 40 issues worth fixing on guthy-renker.com, 15 of them high impact, across 80 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
3.7 s2.4 sMay 16Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20262.9 s
Jun 6, 20263.0 s
Jun 13, 20263.1 s
Jun 20, 20263.2 s
Jun 27, 20263.3 s
Jul 4, 20263.1 s
Jul 11, 20263.2 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.6 s
Aug 15, 20263.4 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s
Sep 19, 20262.8 s
Sep 26, 20263.2 s
Oct 3, 20263.4 s
Oct 10, 20263.2 s
Oct 17, 20262.8 s
Oct 24, 20262.7 s
Oct 31, 20262.6 s

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 guthy-renker.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. guthy-renker.com at 1.9 s1.9 s
  2. guthy-renker.com at 3.8 s3.8 s
  3. guthy-renker.com at 5.8 s5.8 s
  4. guthy-renker.com at 7.7 s7.7 s
  5. guthy-renker.com at 9.6 s9.6 s
  6. guthy-renker.com at 11.5 s11.5 s
  7. guthy-renker.com at 13.4 s13.4 s
  8. guthy-renker.com at 15.3 s15.3 s

Speed

5 to fix54
  • Use efficient cache lifetimes

    3.1 s · 7.8 MB

    56 files are served with short cache lifetimes, so returning visitors download them again (7.8 MB).

  • Render-blocking requests

    1.8 s

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

  • Improve image delivery

    400 ms · 1.9 MB

    16 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Mobile performance score: 54

    54/100

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

  • Adobe TypeKit adds 0 ms

    0 ms

    Adobe TypeKit costs a phone 0 ms of main-thread work and 387 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

    170 ms · 89 KiB

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

  • Reduce unused CSS

    170 ms · 40 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (truyo.com, Cloudflare CDN and JSDelivr CDN and others), adding 538 KiB and 89 ms of main-thread time.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

2 checks passed
  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 139 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

9 to fix100
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 11.8 s

    11.8 s

    Your largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We’re the secret formula behind the beauty brands you love.”.

  • Speed Index: 15.0 s

    15.0 s

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

  • Time to Interactive: 12.2 s

    12.2 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Cumulative Layout Shift: 0.164

    0.164

    The layout shifts by 0.164 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 19 images without width and height

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

5 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 62 ms

    62 ms

    Real visitors wait 62 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.

  • Largest content (LCP) got 13% faster for real visitors

    -13%

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

5 to fix18
  • Page weight: 8.3 MB in 70 requests

    8.3 MB

    Your homepage downloads 8.3 MB in 70 requests on a phone: images 7.6 MB (35), fonts 385 KiB (7) and scripts 225 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    890 KiB

    12 images are downloaded at several times the size a phone draws them, for example m-homepage-hero-ph.jpg at 933 px wide, shown at 226 px. Resized copies would save about 890 KiB.

  • 26 images in older formats

    26 images (6.5 MB) are 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.

  • 13 images below the first screen load straight away

    13 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.4 g of CO₂ per visit

    2.35 g

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

Accessibility

6 to fixGoogle 8391
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

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

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

4 to fixGoogle 7776
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No social preview image

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

  • 16 links with vague text

    16 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 32 internal links, 22 external

    The homepage links to 32 pages on guthy-renker.com and 22 external pages.

5 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “Guthy-Renker | The Industry Leader in Direct Marketing”.

  • Canonical URL set

    The canonical URL is https://www.guthy-renker.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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://www.guthy-renker.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.guthy-renker.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 (578 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix78
  • 10 pages share 5 titles

    https://www.guthy-renker.com/home/our-brands and https://www.guthy-renker.com/our-brands all use the title “Our Brands | Guthy-Renker”, and 4 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://www.guthy-renker.com/home/our-brands, https://www.guthy-renker.com/home/our-story, https://www.guthy-renker.com/home/our-truths, https://www.guthy-renker.com/home/our-culture, https://www.guthy-renker.com/our-story and https://www.guthy-renker.com/our-brands and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.guthy-renker.com/our-story, whose canonical is https://www.guthy-renker.com/home/our-story. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.guthy-renker.com/home/code-of-conduct, https://www.guthy-renker.com/home/privacy-policy, https://www.guthy-renker.com/privacy and https://www.guthy-renker.com/home/terms-conditions have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.guthy-renker.com/home/our-brands and https://www.guthy-renker.com/our-brands have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 11 pages slow to respond

    https://www.guthy-renker.com/home/our-brands, https://www.guthy-renker.com/home/our-story, https://www.guthy-renker.com/home/our-truths, https://www.guthy-renker.com/home/our-culture, https://www.guthy-renker.com/our-story and https://www.guthy-renker.com/our-brands and 5 others took over 3 s to send their HTML from our server.

  • 12 internal pages checked

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

3 checks passed
  • Linked pages load

    All 12 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 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7387
  • 2 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “t(...).validate is not a function”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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.

  • No form on the homepage

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

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

    The homepage carries about 426 words of visible text.

1 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “LEARN MORE”.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 6 other companies contacted

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

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 guthy-renker.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
WordPress
Framework
jQuery
Hosting
AWS

Company

Founded
1988
Headquarters
Santa Monica

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on guthy-renker.com, including 14 speed issues, 4 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