Website review, no card needed
polywood.com website review
Visit site (opens in a new tab)Reviewed 19 November 202632 issues · 67 checks
This review found 32 issues worth fixing on polywood.com, 10 of them high impact, across 67 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.6 s |
| Nov 7, 2026 | 2.7 s |
| Nov 14, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 204 ms |
| Jun 6, 2026 | 204 ms |
| Jun 13, 2026 | 204 ms |
| Jun 20, 2026 | 206 ms |
| Jun 27, 2026 | 214 ms |
| Jul 4, 2026 | 235 ms |
| Jul 11, 2026 | 254 ms |
| Jul 18, 2026 | 278 ms |
| Jul 25, 2026 | 288 ms |
| Aug 1, 2026 | 284 ms |
| Aug 8, 2026 | 286 ms |
| Aug 15, 2026 | 283 ms |
| Aug 22, 2026 | 280 ms |
| Aug 29, 2026 | 271 ms |
| Sep 5, 2026 | 263 ms |
| Sep 12, 2026 | 266 ms |
| Sep 19, 2026 | 271 ms |
| Sep 26, 2026 | 279 ms |
| Oct 3, 2026 | 278 ms |
| Oct 10, 2026 | 271 ms |
| Oct 17, 2026 | 263 ms |
| Oct 24, 2026 | 255 ms |
| Oct 31, 2026 | 248 ms |
| Nov 7, 2026 | 241 ms |
| Nov 14, 2026 | 241 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
Speed
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 242 ms
242 msReal visitors wait 242 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 204 ms to 241 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user TTFB: 598 ms
598 msReal visitors wait 598 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.5 MB
4.5 MBYour homepage downloads 4.5 MB on a phone, 1.0 MB of it images (23%). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Rectangle_1392_5add3f8b-4c19-489f-b104-5c204da80b34.png 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).
About 1.3 g of CO₂ per visit
1.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.28 g of CO₂e: 153.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Form elements must have labels (28 elements)
Form elements must have labels: 28 elements on the page fail this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Main landmark should not be contained in another landmark (3 elements)
Main landmark should not be contained in another landmark: 3 elements on the page fail this check, rated moderate by axe-core.
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.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (5 elements)
Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.
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 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 13 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 2 problems
Structured data found (Organization, VideoObject, WebPage and WebSite) but with 2 problems, for example “VideoObject: thumbnailUrl is not an absolute URL ("//www.polywood.com/cdn/shop/files/preview_images…”.
283 internal links, 24 external
The homepage links to 283 pages on polywood.com and 24 external pages.
6 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “POLYWOOD® waterproof furniture is constructed of genuine POLYWOOD lumber, a proprietary material made in the US using l…”.
Title: 60 characters
Your title is a healthy 60 characters: “POLYWOOD Outdoor Furniture | Patio Furniture Made in the USA”.
Canonical URL set
The canonical URL is https://www.polywood.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://www.polywood.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
3 checks passed
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 (1,688 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.polywood.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://www.polywood.com/collections/black-friday-sale, https://www.polywood.com/pages/wishlist and https://www.polywood.com/collections/kids-dining-furniture have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://www.polywood.com/collections/black-friday-sale, https://www.polywood.com/pages/wishlist, https://www.polywood.com/collections/outdoor-dining-chairs and https://www.polywood.com/collections/outdoor-seating 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 104 found) and read each the way a search engine does.
5 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.
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
10 broken images
10 images failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0707/7147/4659/files/wj7cxznvsquy1hf3sshz.jpg?v=1762872370&width=200&format=webp.
25 small tap targets
25 of 63 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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.
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 923 words of copy
The homepage carries about 923 words of visible text.
3 checks passed
40 calls to action
The homepage has 40 calls to action, for example “Order Status”, “Contact Us” and “Shop All Dining”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 9 testimonial or review blocks and 6 trust badges.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads and 3 mores (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.
40 cookies set on arrival
40Opening the homepage sets 40 cookies, 1 of them by other companies (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.
65 other companies contacted
Loading the homepage contacts 65 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 polywood.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Magento;Magento Enterprise;Shopify;Shopify Plus
- Hosting
- Shopify
Company
- Employees
- 1,279
- Headquarters
- Syracuse
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on polywood.com, including 5 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.