Website review, no card needed
peaktopeakroofing.com website review
Visit site (opens in a new tab)Reviewed 14 November 202614 issues · 77 checks
This review found 14 issues worth fixing on peaktopeakroofing.com, 4 of them high impact, across 77 checks. The most urgent: 18 text elements with low contrast. 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
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 12, 2026 | 152 ms |
| Sep 19, 2026 | 144 ms |
| Sep 26, 2026 | 150 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 144 ms |
| Oct 31, 2026 | 143 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
Mobile performance score: 82
82/100Your mobile performance score is 82. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, openai.com and Google/Doubleclick Ads and others), adding 395 KiB and 743 ms of main-thread time.
Google Tag Manager adds 700 ms
700 msGoogle Tag Manager costs a phone 700 ms of main-thread work and 348 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 361 ms. During a long task the page ignores taps.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
200 ms · 56 KiB5 images could be 56 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused JavaScript
186 KiBAbout 186 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Use efficient cache lifetimes
25 KiB1 file is served with short cache lifetimes, so returning visitors download them again (25 KiB).
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: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Total Blocking Time: 618 ms
618 msScripts block taps and scrolling for 618 ms in total while the page loads. Good is under 200 ms.
Time to Interactive: 6.7 s
6.7 sThe page becomes fully interactive after 6.7 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 152 ms to 143 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 451 ms
451 msReal visitors wait 451 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 2.9 s
2.9 sVisually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.071
0.071The layout barely moves while loading (CLS 0.071, good is under 0.1).
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “Peak to Peak Roofing crew replacing a Denver roof”.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
1 image in older formats
1 image (245 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 0.3 g of CO₂ per visit
0.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.30 g of CO₂e: 36.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.1 MB in 65 requests
1.1 MBYour homepage downloads 1.1 MB in 65 requests on a phone: scripts 639 KiB (40), images 350 KiB (10) and fonts 42 KiB (5). That is a lean page.
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
18 text elements with low contrast
18 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.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
29 links without text
29 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 46 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
93 internal links, 17 external
The homepage links to 93 pages on peaktopeakroofing.com and 17 external pages.
8 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Peak to Peak Roofing & Exteriors is a Denver roofing company for homes and businesses: inspections, repair, replacement…”.
One H1 headline
Your main headline reads: “Residential & Commercial Roofing in Denver - Peak to Peak Roofing”.
Title: 55 characters
Your title is a healthy 55 characters: “Denver Roofing Company & Roofers | Peak to Peak Roofing”.
Canonical URL set
The canonical URL is https://peaktopeakroofing.com/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, ItemList, Person and RoofingContractor.
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://peaktopeakroofing.com/sitemap.xml.
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://peaktopeakroofing.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 (2,931 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
15 of 18 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get A Free Roof Inspection” and “CALL NOW (720) 893-3823”.
9 calls to action
The homepage has 9 calls to action, for example “Contact”, “Get A Free Roof Inspection” and “Call now(720) 893-3823”.
Social proof on the page
Social proof on the homepage: 5 testimonial or review blocks, 1 customer or partner logo, a star rating and 8 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 7 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
8 cookies set on arrival
8Opening the homepage sets 8 cookies, 2 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.
8 other companies contacted
Loading the homepage contacts 8 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 peaktopeakroofing.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
- Tailwind CSS
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 14 issues on peaktopeakroofing.com, including 7 speed issues. 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.