Website review, no card needed

designco.co logo

designco.co website review

Visit site (opens in a new tab)Reviewed 17 November 202639 issues · 87 checks

This review found 39 issues worth fixing on designco.co, 15 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
1.8 s1.3 sMay 30Nov 141.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.5 s
Jun 27, 20261.4 s
Jul 4, 20261.5 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.5 s
Sep 5, 20261.6 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Nov 7, 20261.7 s
Nov 14, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
163 ms87 msMay 30Nov 14137 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026104 ms
Jun 6, 2026104 ms
Jun 13, 202696 ms
Jun 20, 2026104 ms
Jun 27, 2026105 ms
Jul 4, 2026105 ms
Jul 11, 2026119 ms
Jul 18, 2026111 ms
Jul 25, 2026112 ms
Aug 1, 2026112 ms
Aug 8, 2026113 ms
Aug 15, 2026120 ms
Aug 22, 2026119 ms
Aug 29, 2026127 ms
Sep 5, 2026137 ms
Sep 12, 2026137 ms
Sep 19, 2026130 ms
Sep 26, 2026129 ms
Oct 3, 2026129 ms
Oct 10, 2026138 ms
Oct 17, 2026154 ms
Oct 24, 2026153 ms
Oct 31, 2026151 ms
Nov 7, 2026137 ms
Nov 14, 2026137 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 designco.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. designco.co at 1.5 s1.5 s
  2. designco.co at 3.0 s3.0 s
  3. designco.co at 4.6 s4.6 s
  4. designco.co at 6.1 s6.1 s
  5. designco.co at 7.6 s7.6 s
  6. designco.co at 9.1 s9.1 s
  7. designco.co at 10.6 s10.6 s
  8. designco.co at 12.1 s12.1 s

Speed

13 to fix20
  • Reduce unused JavaScript

    2.3 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Google Tag Manager adds 2.3 s

    2.3 s

    Google Tag Manager costs a phone 2.3 s of main-thread work and 1.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 12.7 s

    A phone's processor spends 12.7 s on main-thread work while loading, 6.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 20

    20/100

    Your mobile performance score is 20. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    6.1 MB

    27 images could be 6.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and Facebook and others), adding 2.4 MB and 3.9 s of main-thread time.

  • Use efficient cache lifetimes

    700 ms · 937 KiB

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

  • 20 long tasks on the main thread

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

  • Clarity adds 469 ms

    469 ms

    Clarity costs a phone 469 ms of main-thread work and 29 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.

  • Render-blocking requests

    450 ms

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

  • Facebook adds 301 ms

    301 ms

    Facebook costs a phone 301 ms of main-thread work and 220 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.

  • Shopify adds 274 ms

    274 ms

    Shopify costs a phone 274 ms of main-thread work and 482 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.

  • 1,809 HTML elements

    The page has 1,809 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    150 ms · 37 KiB

    Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 20 KiB

    About 20 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.

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

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

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

  • Real-user CLS: 0.31

    0.31

    For real visitors the layout shifts by 0.31 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 14.7 s

    14.7 s

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

  • Speed Index: 18.8 s

    18.8 s

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

  • Time to Interactive: 36.4 s

    36.4 s

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

  • Total Blocking Time: 2.5 s

    2.5 s

    Scripts block taps and scrolling for 2.5 s in total while the page loads. Good is under 200 ms.

  • Cumulative Layout Shift: 0.258

    0.258

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

  • Tap response (INP) got 32% slower for real visitors

    +32%

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

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

    +21%

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

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 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.

4 checks passed
  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 137 ms

    137 ms

    Real visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 780 ms

    780 ms

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

Images and page weight

1 to fix70
  • Page weight: 10.4 MB in 341 requests

    10.4 MB

    Your homepage downloads 10.4 MB in 341 requests on a phone: images 6.5 MB (48), scripts 2.6 MB (93) and other files 1,008 KiB (168). Under 2 MB keeps phones on slow connections fast.

  • About 2.9 g of CO₂ per visit

    2.94 g

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

3 checks passed
  • 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

4 to fixGoogle 8493
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 12 text elements with low contrast

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 9 links without text

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 46 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: 46 passed and 4 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 8588
  • No social preview image

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

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 2 links with vague text

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

  • One H1 headline

    Your <h1> is empty.

  • 117 internal links, 5 external

    The homepage links to 117 pages on designco.co and 5 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Discover DesignCo in Waco, TX—your trusted flooring and home design store. Shop hardwood, tile, carpet, countertops, an…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “DesignCo | Flooring, Countertops & Home Design in Waco, TX”.

  • Canonical URL set

    The canonical URL is https://designco.co/.

  • 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://designco.co/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://designco.co/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.

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://designco.co/collections/all and https://designco.co/blogs/types-of-countertops have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://designco.co/collections/all and https://designco.co/blogs/types-of-countertops 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 52 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    2 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has a title

    All 2 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 592 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: “GET IN TOUCH” and “APPLY NOW”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Apply for Financing”, “Contact Us” and “Get A Free Estimate”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 18 cookies set on arrival

    18

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

  • 34 other companies contacted

    Loading the homepage contacts 34 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 designco.co, 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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gsc Instagram Feed · Sledge

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

E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Hiring

Hiring
1 open role
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on designco.co, including 24 speed issues, 4 SEO issues and 2 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