Integra Pool Covers — Staging Design & Copy Review

Page-by-page review of the WordPress/Avada staging build at integrapoo1stg.wpenginepowered.com against the intended redesign. Focus areas: color cohesion, button contrast/visibility, content gaps, responsive behavior, and copy (on-brand + keyword-focused).

Prepared by Claude · 2026-06-23 · Method: live desktop render (1920), true 390 px mobile renders (headless + same-origin iframe), in-page contrast/overflow/image diagnostics, and four independent copy/SEO audits. Staging only — production not touched.

Most of what's wrong is systemic — a handful of global theme/template issues repeat on every page. Fixing the ~8 items in Part 1 resolves the majority of what you flagged (clashing colors, dark buttons, gaps, "different on different screens"). Part 2 is the page-by-page detail; Part 3 is the cross-site copy pattern. Severity: Critical launch-blocker · High visible/credibility · Medium polish.

Contents

Part 1Systemic issues — fix these first (they touch every page)

G1The color system is incoherent — multiple competing blues and darksHighColor

This is the root of "the colors don't go together." There are at least four different "brand" colors fighting each other across the site:

  • Logo blue — vivid (the intended brand blue, ~#0F52BA/#0057B7).
  • Button blue #3665AC — a muddy, desaturated mid-blue used for every CTA. It is not the brand blue and reads as dull/washed-out, especially on blue backgrounds.
  • Navy #002B4E (Home hero) and Navy #0A2F54 (Why Integra / Dealer bands) — two different navies.
  • Charcoal #21272C (footer + the Home stat strip).
Fix: Pick ONE action color = the vivid brand blue, ONE dark = a single navy, ONE neutral-dark = the charcoal (footer only). Replace #3665AC on all buttons with the brand blue. Standardize the two navies to one value. This single change does most of the heavy lifting on "colors not going together."
G2Buttons are too dark / low-contrast against backgrounds, and primary↔secondary hierarchy is invertedHighColor / UI

Directly the "buttons too dark to see with the background" complaint:

  • On the dark Home and Become-a-Dealer heroes, the #3665AC filled button sits on navy #002B4E — two close blues, so the button barely separates from the background.
  • Inverted hierarchy (Home hero): the primary "Find a Dealer" is a filled muddy-blue that blends in, while the secondary "Why Integra" has a white border that makes it pop more. The less important button looks more important.
  • "Go to Top" button: brand-blue arrow on dark-gray = 1.8:1 contrast — effectively invisible (WCAG needs ≥3:1 for UI).
Fix: Primary = solid vivid brand blue (or white) that clearly pops off the hero; secondary = outline/ghost. Recolor the Go-to-Top arrow to white. Verify each CTA has obvious separation from whatever sits behind it.
G3Internal developer / staging notes are published as live page copyCriticalCopy

Build notes meant for the developer shipped as visible body copy. A visitor (or Jason/Stuart) reading these instantly loses confidence. Confirmed visible on the live pages:

FAQ: "These answers are page-owned and easy to edit in Avada. No author names, post dates, or old dynamic FAQ entries are used."  ·  "The page now groups common questions by what homeowners usually need to know first."
Service Request: "PRESERVED FORM"  ·  "The service request form remains the operational source of truth. Fields, upload limits, privacy acknowledgement, warranty acknowledgement, notifications, and reCAPTCHA settings are not changed by this page update."  ·  "What stays unchanged / The form workflow remains intact."
Energy Efficient: "Clear numbers, no overpromising"  ·  "The core idea"
Certified Safety: "The Proof Points Stay Visible"
Fix: Delete every one of these. Audit all pages for any heading that describes how the page was built rather than speaking to a customer.
G4reCAPTCHA shows "Invalid domain for site key" and is positioned off the right edgeCriticalForms

On the form pages (Become a Dealer, Service Request — and likely Find a Dealer, Warranty forms) a reCAPTCHA v2 widget (site key 6LdZxIUm…) renders a red "ERROR for site owner: Invalid domain for site key". It's also positioned at x≈1850 — off the right edge of the layout (orphaned, clipped, and creating horizontal overflow on desktop).

Two problems: (1) the widget is visually broken/floating outside the form; (2) the site key isn't authorized for the staging domain, which typically blocks form submission.

Fix: Add integrapoo1stg.wpenginepowered.com (and the production domain) to the reCAPTCHA key's allowed domains, or swap in a staging-valid key. Move the widget back inside the form container. Re-test that each form actually submits.
G5Author bylines + timestamps render on static marketing pagesHighCopy / SEO

Pages display a WordPress author + ISO timestamp as if they were blog posts: "Jan Stevens" (Home, in ld+json), "Will Roberts" (Why Integra, FAQ, Colors), "Matt Frisch" (Service Request), "Eli Bunyi" (Safety, Energy). It looks unfinished and exposes internal accounts.

Fix: Suppress post author + date display on static pages in the Avada template; set page schema author to the organization (Integra Pool Covers), not a person.
G6Section images and footer logos flash blank on load (lazy-load resolving late)HighImages

This is the "images not working" / "gaps in content" symptom. The image files exist and do load given a moment — but lazy-load resolves them late, so on first view (and on quick scroll) several slots render as empty boxes: the Home dual-audience columns, the Home "Engineered to Last" center, the Why-Integra "All-Stainless Engineering" right column, and both footer logos (Integra white + Explore). (Note: these are NOT 404s — the files are present; it's a rendering/lazy-load timing bug.)

Fix: Disable lazy-load for above-the-fold and section "hero" images and for the footer logos (Avada → Performance, or add loading="eager" / skip-lazy class). Preload the hero image. After the change, hard-reload and confirm no blank boxes appear.
G7Heavy dead whitespace and unequal blocks between sectionsHighLayout

"Gaps in content," confirmed repeatedly: oversized empty bands between sections (Home stat row floats in a white void; Service Request hero has a large empty band below the buttons; Become-a-Dealer feature section has a tall empty area below the image). Several card rows are also unequal height (see Home G/cards).

Fix: Tighten section vertical padding to a consistent scale; set card columns to equal height; fill or remove empty columns. Aim for an even rhythm top-to-bottom.
G8The same component looks different on different pagesMediumConsistency

Inconsistency makes the site feel "completely different page to page":

  • The 4-stat strip sits on near-black (Home), navy (Why Integra / Dealer), and light (FAQ) — same component, three backgrounds.
  • The hero photo is heavily darkened to near-unreadable on Home & Become-a-Dealer, but light/clear on Why Integra, FAQ, Service Request (see H1).
  • FAQ topic-card numbers render in random off-brand colors (01 blue, 02 orange, 03 purple, 04 brown).
  • CTA capitalization mixes Title Case and sentence case across pages.
Fix: Lock one treatment per component (one stat-strip background, one hero overlay opacity, one accent color, Title Case buttons everywhere).
G9Footer legal line exposes parent + vendor and appears on form-less pagesMediumCopy / Legal

The consent line — "…you consent to Explore Industries USA, Inc. sending your personal contact information to our third-party merchant partners including but not limited to Vistafi Solutions, LLC." — is clinical, breaks brand separation on a consumer page, and renders on pages with no form (FAQ, Colors), where it references "completing this form" that doesn't exist.

Fix: Have legal confirm wording; show it only adjacent to actual forms; style as fine print. Also confirm whether the parent/vendor names should appear on the consumer-facing brand at all.
G10Mixed canonical domains on stagingMediumSEO

Why Integra's canonical points to the production domain (integrapoolcovers.com/why-integra/) while Home's canonical points to the staging subdomain. Mixed canonicals will leak/confuse SEO equity if launched as-is.

Fix: Make all canonicals consistent (all production on launch, all staging while staging). Verify before go-live.

Part 2Page-by-page

Each page lists page-specific visual issues I observed plus the highest-impact copy fixes (with paste-ready rewrites). The full per-section copy rewrites are extensive — the worst offenders are here; ask if you want the complete line-by-line set for any page.

Home /

H1Hero photo is buried under a too-dark navy overlayHighVisual

The hero (hero-pool-cover-aerial.webp) sits under a heavy #002B4E overlay — the subject is unreadable (it just looks like dark blue blobs), and it's an aerial of umbrellas/patio rather than an obvious automatic-cover hero shot. Why-Integra uses the same style image with a far lighter overlay (legible). Fix: reduce the overlay opacity to ~40–55% so the cover is visible; standardize hero overlay across pages; consider a hero that clearly shows a closed automatic cover.

H2Hero buttons blend in + inverted hierarchy; floating "custom-fit" box looks detachedHighVisual

See G1/G2 — both buttons are the same muddy fill; secondary out-pops primary. The pale "Custom-fit automatic covers…" pill floats below the buttons disconnected from everything. Fix: real primary/secondary styling; integrate or remove the floating box.

H3Stat row floats in a white void; benefit cards are unequal height & flatHighVisual

The 4-item stat row (ASTM F1346 / All-stainless / 20-Year / 7-Year) sits alone with large empty space above and below. The "Why Homeowners Choose…" cards are unequal height (Cleaner Water hangs lower) and visually flat (faint fill + thin top border only). Fix: tighten spacing, equalize card heights, give cards a clearer card style.

H4"Engineered to Last" has an empty center; dual-audience split shows blank image boxesHighVisual

The "Engineered to Last" row renders with a large empty center column (image slot) between the two text blocks; the "Peace of Mind, Automated" / "Add a Certified Cover Line" split shows empty white boxes where images belong (lazy-load, G6). Fix: per G6, plus ensure the center column has its image or collapse the layout.

H5Copy — strong H1, but weak CTAs, hedged safety claims, and a cliché section headMediumCopy

H1 "Automatic Pool Safety Covers, Built to a Higher Standard" is good — keep it. Problems:

"Learn More About Integra" / "Why Integra" (buttons) — weakest possible CTA labels.
→ "See What Makes Integra Different" / "See How It Works".
"…sits taut across your pool to help create a barrier…" and FAQ "…helping create a safer barrier…" — hedging undercuts an ASTM-certified safety product.
→ "…sits taut across your pool, creating a certified barrier…". Use definitive language anywhere the cover's barrier function is described.
"Engineered to Last, Certified to Protect" and "Quality Controlled from the Roll to the Rail" — generic/wordplay headings.
→ "What Sets Integra Apart" and "Made in Knoxville, Tennessee".

Card 4 "Pool Protection / Shield your pool from the elements…" is vague boilerplate; "Peace of Mind, Automated" is a weak H2. Full rewrites available.

Why Integra /why-integra/

W1"All-Stainless Engineering" section has a large empty image box on the rightHighVisual

On first render the right column is an empty light-blue rectangle (lazy-load, G6). The navy stat band here (#0A2F54) is also a different navy than the Home hero (#002B4E) — see G1/G8.

W2Copy — H1 isn't keyword-bearing; "proof hub" is internal language; weak CTAsMediumCopy
H1: "A certified safety cover that closes with the flip of a switch." — no "automatic pool cover" / "ASTM" in the page's main heading.
→ "What Sets Integra Apart" or "The Proof Behind Integra Automatic Pool Safety Covers".
"The proof hub for Integra safety, strength, fit, and everyday use." + "Use this page as the starting point…" — describes the page to itself.
→ "Everything you need to evaluate Integra — safety, materials, fit, and efficiency in one place." (drop the "use this page…" instruction).
CTAs "Ask about your pool", "Start with a dealer" — vague/inconsistent; "flip of a switch" appears again here (see Part 3).

Certified Automatic Pool Safety Covers /why-integra/certified-automatic-pool-safety-covers/

S1Leaked dev note + heavy hedging on the page that most needs authorityHighCopy
"The Proof Points Stay Visible" — internal design note (delete; see G3).
"…designed to act as a barrier…", "…helping keep the surface covered…", "Aegis fabric is built to help water drain…" — three hedges on a certified safety page.
→ State it plainly: "When closed, it forms a continuous barrier across your pool's surface…"; "…drains water off the surface…". ASTM certification is the proof — don't soften it.
Heading "Certified Safety for Peace of Mind" as the H1 — tagline, not keyword-led.
→ H1 "ASTM F1346 Certified Automatic Pool Safety Covers"; work "peace of mind" into body, not the H1.
S2Content gaps: no load rating, no install process, Aegis never explained, no proofMediumCopy / Content

The page never states a weight/load capacity (the most concrete safety proof), never explains what "Aegis fabric" is, and has no install-process line and no testimonial/social proof. The FAQ "How much weight can a cover hold?" also dodges the question. Fix: add a load-rating statement (or explain the ASTM requirement), a one-line install overview, an Aegis definition, and one piece of social proof.

Energy Efficient Pool Covers /why-integra/energy-efficient/

E1Leaked dev notes; good stats but jargon + no dollar figureMediumCopy
"Clear numbers, no overpromising" and "The core idea" — internal notes (delete; see G3).

The DOE-sourced stats (up to 90% evaporation, 50–70% heating, 35–60% chemicals) are the page's strength — keep them. But: "Less make-up water" is industry jargon (→ "Less water to replace over a season"); "Chemicals work longer" is imprecise (→ "Chemical balance holds longer"); CTA "Ready to compare options?" opens a new research loop (→ "Make Daily Pool Covering a Habit"). Add an illustrative dollar example to make savings concrete.

Become a Dealer /become-a-dealer/

BD1reCAPTCHA invalid-domain error visible; dark hero; unbalanced feature blockCriticalVisual / Forms

The red reCAPTCHA "Invalid domain" error bleeds in at the right edge (G4) — and on a dealer-application page that likely means the form won't submit. The hero is the over-darkened aerial (H1-style). "Why Dealers Stand Behind It" is a flat text list with a small image and a tall empty area beneath it. Fix: G4 first; then style the feature list as proper cards/icons and balance the column.

BD2Copy talks product, never the dealer's business; form grammar errorHighCopy

The whole page sells the product to a builder who already knows ASTM — but never the dealer value (margin, territory, leads, training, support, co-op marketing). The four feature cards are the same ones used on the homeowner "Find a Dealer" page (audience bleed).

Form field: "What Regions are You Serving / Intending Serve?" — grammar error (missing "to").
→ "What Regions Are You Serving or Plan to Serve?"  ·  Add a "What You Get as an Integra Dealer" section (territory, training, co-branded marketing, dealer-locator leads, 20-yr warranty story, margin). Differentiate from the homeowner page.

Also: "fabric quality your customers can understand" (condescending); descriptions that restate their own headline; "next appropriate step" hedge; "Round out patios… with an integrated cover" (pun on the brand name).

Find a Dealer /find-a-dealer/

FD1No dealer map/locator; form-first framing; no phone/response-timeHighCopy / Content

The biggest gap: a homeowner searching "pool cover dealer near me" expects a zip search / map of nearby dealers — this page only has a lead form, and the H2 "Start With the Form" never says what comes back. There's no expected response time, no visible phone number (the footer's (865) 281-1746 isn't referenced), and no link to Colors before they commit. Fix: add a locator (or set expectations: "We'll connect you with a dealer in your area within 1 business day"), surface a phone option, and link to Colors.

FD2Copy — directive CTAs, "Back to the Form", warranty cards restate themselvesMediumCopy
"Start With the Form" / closing button "Back to the Form" — navigation labels, not CTAs; "Universal inground fit" badge contradicts "custom fit" elsewhere.
→ "Connect With a Local Dealer"; "Custom Fit for Your Pool". The "Daily Convenience" item is filed under Warranty cards — move it out.

Colors /colors/

C1"Compare all seven colors" grid is broken on mobile and messy on desktopHighVisual / Responsive

This is the clearest "looks completely different on different screens" case. On desktop the section duplicates the top swatch box, lays the 7 cards into uneven rows with ~2 empty card cells, and the "Charcoal" heading clips at its card edge. On mobile (verified at a true 390 px viewport) the cards collapse into two ragged, staggered columns that look overlapping and broken. (There is no horizontal page overflow — scrollWidth fits — the grid layout itself is the problem.) Fix: rebuild as a single responsive equal-height grid (3-up desktop → 2-up tablet → 1-up mobile) with the heading above the grid, not inside it; remove the empty cells; and decide whether the top swatch box and the card grid are both needed (they're redundant).

C2"Light Grey" vs "Light Gray" inconsistency; off-brand "beautiful"; color copy lacks pairingsMediumCopy
Top swatch label "Light Grey" vs card heading "Light Gray" — same color, two spellings.
"Seven beautiful colors, one trusted fabric." — "beautiful" is off-brand filler. Descriptions like Royal Blue "reads instantly as pool" are copy-speak, and several colors don't pair to a decking/landscape style (the established Integra pattern).
→ Standardize to "Light Gray" site-wide; "Seven colors. One fabric standard."; give each color a specific material pairing (e.g., "Charcoal — pairs with bluestone, concrete, or charcoal pavers").

FAQ /frequently-asked-questions/

F1Two leaked dev notes visible; topic-card numbers in random off-brand colorsCriticalCopy / Visual

The "page-owned… in Avada / no author names…" and "The page now groups common questions…" notes are visible (G3). The topic-card numbers render 01 blue / 02 orange / 03 purple / 04 brown — a rainbow that isn't in the brand palette (G1/G8). Fix: delete the notes; recolor the numbers to the single brand blue (or a tasteful neutral).

F2Answers that dodge the question + missing high-volume FAQsMediumCopy

"How much weight can a cover hold?" pivots to water level instead of answering. Missing the highest-volume searches: cost, install time, "what does ASTM F1346 mean", repair/service, and color names. Fix: answer the weight question (cite the ASTM requirement), and add cost / install-time / ASTM-explainer / repair FAQs.

Service Request /service-request/

SR1Multiple leaked dev notes; reCAPTCHA error; dead space; broken field labelCriticalCopy / Forms

"PRESERVED FORM", "…operational source of truth… reCAPTCHA settings are not changed by this page update", and "What stays unchanged / The form workflow remains intact" are all visible (G3). The reCAPTCHA invalid-domain error shows here too (G4). Large empty band below the hero. And a broken form label:

Field label "Installed Phone" — truncated/nonsensical.
→ "Installer Phone" (or "Dealer / Installer Phone"). Delete all the staging notes; fix reCAPTCHA; tighten the hero spacing. Also add an expected response time and a phone fallback for urgent (cover stuck / pool unsecured) cases.

Blog & posts /blog/ · /swimming-pool-covers/…

BL1Post template renders OK; legacy titles are corny / off-brandMediumCopy

The post template itself renders fine on desktop and mobile. The legacy post titles are the corniest copy on the site — e.g. "Dive into Style: Choosing the Perfect Color…", "Seal the Deal…", "Winter Armor: Elevating Pool Protection…", "Refresh and Revive…". These read as blog-clickbait, not the quietly-premium Integra voice, and several bury the keyword. Fix: rename to plain, search-led titles (e.g., "Automatic Pool Cover Colors: How to Choose", "Winterizing Your Automatic Pool Cover"). Lower priority than the page work above.

Part 3Cross-site copy patterns

Fair balanceWhat's already working

Priority order for Codex: G3 + G4 + SR1/BD1 (remove dev notes, fix reCAPTCHA — launch blockers) → G1 + G2 (color/button system) → G6 + G7 (lazy-load + spacing) → C1 (Colors grid) → G5/G8/G10 (bylines, consistency, canonicals) → copy pass per page. Everything here was verified on the live staging build on 2026-06-23.