Website review, no card needed
copperstate.com website review
Visit site (opens in a new tab)Reviewed 18 November 202645 issues · 85 checks
This review found 45 issues worth fixing on copperstate.com, 12 of them high impact, across 85 checks. The most urgent: page weight: 10.8 MB in 69 requests. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.5 s |
| Nov 14, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 77 ms |
| Jun 6, 2026 | 79 ms |
| Jun 13, 2026 | 78 ms |
| Jun 20, 2026 | 79 ms |
| Jun 27, 2026 | 79 ms |
| Jul 4, 2026 | 78 ms |
| Jul 11, 2026 | 79 ms |
| Jul 18, 2026 | 79 ms |
| Jul 25, 2026 | 78 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 78 ms |
| Aug 22, 2026 | 79 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 79 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 78 ms |
| Oct 3, 2026 | 75 ms |
| Oct 10, 2026 | 78 ms |
| Oct 17, 2026 | 77 ms |
| Oct 24, 2026 | 78 ms |
| Oct 31, 2026 | 78 ms |
| Nov 7, 2026 | 76 ms |
| Nov 14, 2026 | 78 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
4 third-party services on the page
4 third-party services load with your homepage (dynamics365commerce.ms, dynamics.com and Google Fonts and others), adding 10.6 MB and 618 ms of main-thread time.
Reduce unused JavaScript
310 ms · 707 KiBAbout 707 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
dynamics.com adds 0 ms
0 msdynamics.com costs a phone 0 ms of main-thread work and 9.2 MB 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.
dynamics365commerce.ms adds 618 ms
618 msdynamics365commerce.ms costs a phone 618 ms of main-thread work and 1.3 MB 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
650 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 650 ms.
Improve image delivery
450 ms · 69 KiB2 images could be 69 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 505 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 53 KiBPolyfills for old browsers add 53 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 34 KiB8 files are served with short cache lifetimes, so returning visitors download them again (34 KiB).
Reduce unused CSS
63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 833 ms of it running JavaScript. That is comfortably low.
Server response: 155 ms
155 msYour server sent the HTML in 155 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 264 ms
264 msScripts block taps and scrolling for 264 ms in total while the page loads. Good is under 200 ms.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 77 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 97 ms
97 msReal visitors wait 97 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 10.8 MB in 69 requests
10.8 MBYour homepage downloads 10.8 MB in 69 requests on a phone: media 9.1 MB (6), scripts 1.1 MB (42) and fonts 325 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (57 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 3.1 g of CO₂ per visit
3.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.06 g of CO₂e: 367.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 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
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
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.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
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.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (19 characters)
Your title is only 19 characters: “Home | Copper State”. 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 social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.copperstate.com/sitemap.xml, so Google discovers your pages only by following links.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
39 internal links, 1 external
The homepage links to 39 pages on copperstate.com and 1 external page.
2 checks passed
Canonical URL set
The canonical URL is https://www.copperstate.com/.
robots.txt in place
robots.txt is in place.
AI search readiness
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.copperstate.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.
2 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 (553 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a title
https://www.copperstate.com/partner-request, https://www.copperstate.com/contact, https://www.copperstate.com/products, https://www.copperstate.com/locations, https://www.copperstate.com/construction and https://www.copperstate.com/manufacturers and 9 others have no <title>, so Google invents the link text in results.
15 pages without a meta description
https://www.copperstate.com/partner-request, https://www.copperstate.com/contact, https://www.copperstate.com/products, https://www.copperstate.com/locations, https://www.copperstate.com/construction and https://www.copperstate.com/manufacturers and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.copperstate.com/partner-request, https://www.copperstate.com/contact, https://www.copperstate.com/products, https://www.copperstate.com/locations, https://www.copperstate.com/construction and https://www.copperstate.com/manufacturers and 9 others 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 23 found) and read each the way a search engine does.
3 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
5 small tap targets
5 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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”.
Missing source maps
Large scripts ship without source maps.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
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 528 words of copy
The homepage carries about 528 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “PARTNER REQUEST” and “CONTACT”.
5 calls to action
The homepage has 5 calls to action, for example “PARTNER REQUEST”, “CONTACT” and “Learn More”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
7 other companies contacted
Loading the homepage contacts 7 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 copperstate.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- React
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on copperstate.com, including 17 speed issues, 8 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.