Website review, no card needed

houstonacrylic.com logo

houstonacrylic.com website review

Visit site (opens in a new tab)Reviewed 6 November 202626 issues · 77 checks

This review found 26 issues worth fixing on houstonacrylic.com, 8 of them high impact, across 77 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
1.2 s819 msMay 16Oct 31890 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 2026998 ms
Jun 20, 20261.0 s
Jun 27, 20261.0 s
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 2026994 ms
Jul 25, 2026982 ms
Aug 1, 2026953 ms
Aug 8, 2026923 ms
Aug 15, 2026907 ms
Aug 22, 2026907 ms
Aug 29, 2026916 ms
Sep 5, 2026905 ms
Sep 12, 2026914 ms
Sep 19, 2026897 ms
Sep 26, 2026886 ms
Oct 3, 2026888 ms
Oct 10, 2026860 ms
Oct 17, 2026872 ms
Oct 24, 2026883 ms
Oct 31, 2026890 ms
Real-visitor tap response (INP)75th percentile, phones
85 ms68 msMay 16Oct 3170 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202680 ms
May 30, 202683 ms
Jun 6, 202682 ms
Jun 13, 202679 ms
Jun 20, 202679 ms
Jun 27, 202676 ms
Jul 4, 202673 ms
Jul 11, 202674 ms
Jul 18, 202672 ms
Jul 25, 202674 ms
Aug 1, 202672 ms
Aug 8, 202670 ms
Aug 15, 202670 ms
Aug 22, 202670 ms
Aug 29, 202670 ms
Sep 5, 202671 ms
Sep 12, 202671 ms
Sep 19, 202671 ms
Sep 26, 202671 ms
Oct 3, 202671 ms
Oct 10, 202671 ms
Oct 17, 202670 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 houstonacrylic.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. houstonacrylic.com at 0.5 s0.5 s
  2. houstonacrylic.com at 1.1 s1.1 s
  3. houstonacrylic.com at 1.6 s1.6 s
  4. houstonacrylic.com at 2.2 s2.2 s
  5. houstonacrylic.com at 2.7 s2.7 s
  6. houstonacrylic.com at 3.2 s3.2 s
  7. houstonacrylic.com at 3.8 s3.8 s
  8. houstonacrylic.com at 4.3 s4.3 s

Speed

8 to fix65
  • Render-blocking requests

    1.8 s

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

  • 3,546 HTML elements

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

  • Reduce unused JavaScript

    970 ms · 267 KiB

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

  • Mobile performance score: 65

    65/100

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

  • Improve image delivery

    450 ms · 23 KiB

    1 image could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Use efficient cache lifetimes

    400 ms · 34 KiB

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

  • Main-thread work: 2.4 s

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

  • Shopify adds 30 ms

    30 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Amazon Web Services, negate.io and Shopify and others), adding 630 KiB and 330 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 29 KiB

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

  • 2 long tasks on the main thread

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

  • 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: 7 ms

    7 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 8.8 s

    8.8 s

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

  • Time to Interactive: 8.8 s

    8.8 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Speed Index: 5.4 s

    5.4 s

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

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.2 s

    1.2 s

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

  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 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.1 s

    1.1 s

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

  • Real-user TTFB: 477 ms

    477 ms

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

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

    -12%

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

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

    -20%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 16 ms

    16 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.0 MB in 159 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 159 requests on a phone: other files 874 KiB (77), scripts 640 KiB (60) and images 241 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.57 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.9 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

3 to fixGoogle 9395
  • 3 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 517 images in the HTML carry an alt attribute.

  • 47 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: 47 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

4 to fixGoogle 10079
  • Title is short (15 characters)

    Your title is only 15 characters: “Houston Acrylic”. 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 (34 characters)

    Your meta description is only 34 characters: “Your source for acrylic in Houston”. 70 to 160 characters is enough to sell the click.

  • One H1 headline

    Your <h1> is empty.

  • 273 internal links, 25 external

    The homepage links to 273 pages on houstonacrylic.com and 25 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://houstonacrylic.com/.

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

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,287 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://houstonacrylic.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 13 pages without a meta description

    https://houstonacrylic.com/collections/acrylic, https://houstonacrylic.com/collections/new-arrivals, https://houstonacrylic.com/collections/all, https://houstonacrylic.com/collections/co2, https://houstonacrylic.com/collections/diode and https://houstonacrylic.com/collections/fiber and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 116 found) and read each the way a search engine does.

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 small tap targets

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

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

3 to fix78
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • No analytics detected

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 259 words of copy

    The homepage carries about 259 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: “SHOP MATERIALS”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Last Call”, “Join the Facebook Group” and “Contact Us”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage, asking for an email.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • 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

  • 6 cookies set on arrival

    6

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 houstonacrylic.com, 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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Simple Affiliate · Forms · Globo Product Options · amazonaws.com

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
Hosting
Shopify

Company

Headquarters
Houston

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on houstonacrylic.com, including 12 speed issues, 4 SEO issues and 3 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