Website review, no card needed

pergo.com logo

pergo.com website review

Visit site (opens in a new tab)Reviewed 31 October 202630 issues · 63 checks

This review found 30 issues worth fixing on pergo.com, 7 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

Real-visitor load time (LCP)75th percentile, phones
4.1 s2.4 sMay 9Oct 242.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
May 16, 20263.5 s
May 23, 20263.8 s
May 30, 20263.8 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20263.7 s
Jul 4, 20263.9 s
Jul 11, 20263.6 s
Jul 18, 20263.5 s
Jul 25, 20263.2 s
Aug 1, 20263.4 s
Aug 8, 20263.2 s
Aug 15, 20263.0 s
Aug 22, 20263.1 s
Aug 29, 20263.0 s
Sep 5, 20263.1 s
Sep 12, 20263.3 s
Sep 19, 20263.3 s
Sep 26, 20263.1 s
Oct 3, 20263.2 s
Oct 10, 20263.0 s
Oct 17, 20262.7 s
Oct 24, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
126 ms94 msMay 16Oct 24106 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026118 ms
May 23, 2026113 ms
May 30, 2026113 ms
Jun 6, 2026106 ms
Jun 13, 2026105 ms
Jun 20, 2026105 ms
Jun 27, 2026111 ms
Jul 4, 2026119 ms
Jul 11, 2026120 ms
Jul 18, 2026122 ms
Jul 25, 2026113 ms
Aug 1, 2026107 ms
Aug 8, 2026113 ms
Aug 15, 2026112 ms
Aug 22, 2026111 ms
Aug 29, 2026113 ms
Sep 5, 2026116 ms
Sep 12, 2026112 ms
Sep 19, 2026111 ms
Sep 26, 2026104 ms
Oct 3, 202698 ms
Oct 10, 202698 ms
Oct 17, 2026100 ms
Oct 24, 2026106 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 pergo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix71
  • Render-blocking requests

    1.9 s

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

  • Reduce unused JavaScript

    1.2 s · 273 KiB

    About 273 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 71

    71/100

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

  • Reduce unused CSS

    600 ms · 203 KiB

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

  • Google Tag Manager adds 348 ms

    348 ms

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

    292 KiB

    1 image could be 292 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Bing Ads and Visual Studio and others), adding 493 KiB and 367 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Use efficient cache lifetimes

    19 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (19 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.

2 checks passed
  • Main-thread work: 0.7 s

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

8 to fix67
  • 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: 7.0 s

    7.0 s

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

  • Time to Interactive: 7.6 s

    7.6 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user FCP: 2.4 s

    2.4 s

    Real visitors see the first content after 2.4 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.

  • Speed Index: 4.9 s

    4.9 s

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

6 checks passed
  • Real-user INP: 102 ms

    102 ms

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

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

    -11%

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

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

    -24%

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

  • Total Blocking Time: 95 ms

    95 ms

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

2 to fix86
  • An image on the first screen is lazy-loaded

    pergo-v4007-40017-grey-vinyl-floor-bedroom-2300x1534.ashx is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    245 KiB

    1 image is downloaded at several times the size a phone draws it, for example pergo-v4007-40017-grey-vinyl-floor-bedroom-2300x1534.ashx at 2,300 px wide, shown at 374 px. Resized copies would save about 245 KiB.

  • 1 image in older formats

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

    0.34 g

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

1 checks passed
  • Page weight: 1.2 MB in 66 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 66 requests on a phone: scripts 555 KiB (8), images 409 KiB (49) and stylesheets 228 KiB (2). That is a lean page.

Accessibility

1 to fixGoogle 10098
  • 70 links without text

    70 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 59 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

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

SEO

5 to fixGoogle 10078
  • Title is short (27 characters)

    Your title is only 27 characters: “Pergo, Floors for Real Life”. 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.

  • No XML sitemap

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

  • Only 0 internal links

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

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

4 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “We invented laminate flooring back in 1977 and have continued to lead the way in durable floors ever since. For your ho…”.

  • Canonical URL set

    The canonical URL is https://www.pergo.com/en.

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

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://www.pergo.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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Best practices

1 to fixGoogle 9293
  • 70 small tap targets

    70 of 72 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.

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

5 to fix42
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 16 words

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

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

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

  • 4 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on pergo.com, including 14 speed issues, 5 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