Website review, no card needed
duffeyse.com website review
Visit site (opens in a new tab)Reviewed 19 October 202647 issues · 84 checks
This review found 47 issues worth fixing on duffeyse.com, 21 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
74C- #82,811 of 117,924 reviewed websitesbeats 26%
- #52,489 of 67,048 online storesbeats 18%
- #618 of 1,422 Squarespace websitesbeats 47%
Closest competitors among online stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.2 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 3.0 s |
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
Improve image delivery
7.7 s · 7.2 MB22 images could be 7.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.7 s faster on a phone.
Reduce unused JavaScript
7.5 s · 958 KiBAbout 958 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.5 s faster on a phone.
Render-blocking requests
3.4 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Reduce unused CSS
1.2 s · 236 KiBAbout 236 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Use efficient cache lifetimes
1.2 s · 211 KiB15 files are served with short cache lifetimes, so returning visitors download them again (211 KiB).
Mobile performance score: 47
47/100Your mobile performance score is 47 (desktop: 66). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Squarespace, Google CDN and Facebook and others), adding 2.3 MB and 1.6 s of main-thread time.
Squarespace adds 496 ms
496 msSquarespace costs a phone 496 ms of main-thread work and 1.1 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.
Legacy JavaScript
450 ms · 121 KiBPolyfills for old browsers add 121 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Google CDN adds 380 ms
380 msGoogle CDN costs a phone 380 ms of main-thread work and 733 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 213 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: 79 ms
79 msYour server sent the HTML in 79 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.
First Contentful Paint: 16.6 s
16.6 sThe first text or image appears after 16.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 44.0 s
44.0 sYour largest element takes 44.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “2021-10-29 - TierPoint Completed Project-1002.jpg”.
Speed Index: 16.6 s
16.6 sVisually, the page fills in at 16.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 46.8 s
46.8 sThe page becomes fully interactive after 46.8 s. Good is under 3.8 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 802 ms
802 msReal visitors wait 802 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 340 ms
340 msScripts block taps and scrolling for 340 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
2 checks passed
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.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 11.1 MB in 165 requests
11.1 MBYour homepage downloads 11.1 MB in 165 requests on a phone: images 7.6 MB (28), scripts 2.2 MB (65) and other files 701 KiB (46). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 6.2 MB together. On a phone connection a single image that size takes seconds.
10 images far larger than shown
5.1 MB10 images are downloaded at several times the size a phone draws them, for example data-technology.png at 1,920 px wide, shown at 330 px. Resized copies would save about 5.1 MB.
15 images below the first screen load straight away
15 images further down the page (6.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.1 g of CO₂ per visit
3.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.15 g of CO₂e: 377.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
46 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: 46 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (29 characters)
Your title is only 29 characters: “Duffey Southeast Construction”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (288 characters)
Your meta description is 288 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (GeneralContractor, LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5fde576610915253365…”.
47 internal links, 12 external
The homepage links to 47 pages on duffeyse.com and 12 external pages.
5 checks passed
One H1 headline
Your main headline reads: “BUILDING BEYOND EXPECTATIONS”.
Canonical URL set
The canonical URL is https://www.duffeyse.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.duffeyse.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (323 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.duffeyse.com/llms.txt (5 KiB, 12 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://www.duffeyse.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
3 linked pages hidden from search
https://www.duffeyse.com/retail-restaurant, https://www.duffeyse.com/privacy-policy and https://www.duffeyse.com/feedback are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
/ and https://www.duffeyse.com/home all use the title “Duffey Southeast Construction”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.duffeyse.com/our-approach has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.duffeyse.com/feedback has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.duffeyse.com/home has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
2 checks passed
Linked pages load
All 14 pages we checked loaded without an error.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Unexpected token ')'”.
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.
Thin social proof
Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 233 words
The homepage has only about 233 words of visible text; thin pages give Google and first-time buyers little to go on.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
7 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Sign Up”, “Contact” and “View Full Contact Info”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel, Microsoft Clarity, LinkedIn Insight and Umami.
Direct contact links
Visitors can reach you directly: 12 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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
29 other companies contacted
Loading the homepage contacts 29 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 duffeyse.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Squarespace
- Framework
- jQuery
- Analytics
- Google Analytics | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on duffeyse.com, including 22 speed issues, 3 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.