Website review, no card needed
dsldhomes.com website review
Visit site (opens in a new tab)Reviewed 17 November 202634 issues · 89 checks
This review found 34 issues worth fixing on dsldhomes.com, 15 of them high impact, across 89 checks. The most urgent: google Tag Manager adds 1.5 s. 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.2 s |
| Jun 6, 2026 | 4.2 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.4 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.4 s |
| Nov 7, 2026 | 3.3 s |
| Nov 14, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 278 ms |
| Jun 6, 2026 | 266 ms |
| Jun 13, 2026 | 273 ms |
| Jun 20, 2026 | 274 ms |
| Jun 27, 2026 | 287 ms |
| Jul 4, 2026 | 288 ms |
| Jul 11, 2026 | 287 ms |
| Jul 18, 2026 | 283 ms |
| Jul 25, 2026 | 271 ms |
| Aug 1, 2026 | 263 ms |
| Aug 8, 2026 | 261 ms |
| Aug 15, 2026 | 254 ms |
| Aug 22, 2026 | 262 ms |
| Aug 29, 2026 | 271 ms |
| Sep 5, 2026 | 272 ms |
| Sep 12, 2026 | 274 ms |
| Sep 19, 2026 | 276 ms |
| Sep 26, 2026 | 275 ms |
| Oct 3, 2026 | 282 ms |
| Oct 10, 2026 | 292 ms |
| Oct 17, 2026 | 296 ms |
| Oct 24, 2026 | 295 ms |
| Oct 31, 2026 | 277 ms |
| Nov 7, 2026 | 254 ms |
| Nov 14, 2026 | 246 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.7 s
1.5 s
2.2 s
2.9 s
3.6 s
4.4 s
5.1 s
5.8 s
Speed
Google Tag Manager adds 1.5 s
1.5 sGoogle Tag Manager costs a phone 1.5 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.4 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.1 s
A phone's processor spends 6.1 s on main-thread work while loading, 3.2 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 (Google Tag Manager, Facebook and Lucky Orange and others), adding 1.9 MB and 1.9 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
787 KiB13 images could be 787 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 734 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
292 KiB15 files are served with short cache lifetimes, so returning visitors download them again (292 KiB).
Reduce unused CSS
150 ms · 106 KiBAbout 106 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
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: 292 ms
292 msYour server sent the HTML in 292 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: 13.0 s
13.0 sThe first text or image appears after 13.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 13.6 s
13.6 sYour largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “That Fits Your Lifestyle”. Most of its time is element render delay (5.5 s).
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 35.8 s
35.8 sThe page becomes fully interactive after 35.8 s. Good is under 3.8 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 288 ms
288 msReal visitors wait 288 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 925 ms
925 msReal visitors wait 925 ms for your server to start answering (75th percentile). Good is under 800 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 278 ms to 246 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Largest content (LCP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.2 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.8 MB in 211 requests
6.8 MBYour homepage downloads 6.8 MB in 211 requests on a phone: scripts 2.7 MB (42), HTML 2.1 MB (6) and images 1.8 MB (78). Under 2 MB keeps phones on slow connections fast.
15 images below the first screen load straight away
15 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
11 images far larger than shown
13 KiB11 images are downloaded at several times the size a phone draws them, for example 720 at 1,080 px wide, shown at 358 px. Resized copies would save about 13 KiB.
About 1.9 g of CO₂ per visit
1.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.94 g of CO₂e: 232.5 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
Scrollable region must have keyboard access (7 elements)
Scrollable region must have keyboard access: 7 elements on the page fail this check, rated serious by axe-core.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 15 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
9 links with vague text
9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
91 internal links, 6 external
The homepage links to 91 pages on dsldhomes.com and 6 external pages.
8 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Explore home builders focused on quality, efficiency & long-term value with DSLD Homes. Discover new homes for sale in …”.
One H1 headline
Your main headline reads: “Trusted Home Builders For Modern Living And Comfort”.
Title: 52 characters
Your title is a healthy 52 characters: “Trusted Home Builders For Modern Living | DSLD Homes”.
Canonical URL set
The canonical URL is https://www.dsldhomes.com/.
Structured data in place
Structured data found: HomeAndConstructionBusiness, LocalBusiness and Organization.
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.dsldhomes.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.dsldhomes.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.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,255 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages slow to respond
https://www.dsldhomes.com/homebuying-guide, https://www.dsldhomes.com/path-to-ownership, https://www.dsldhomes.com/construction-process and https://www.dsldhomes.com/customize-your-new-home took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 33 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
5 small tap targets
5 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 1,256 words of copy
The homepage carries about 1,256 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More” and “Shop For Homes”.
8 calls to action
The homepage has 8 calls to action, for example “Learn More”, “Submit a Request” and “Contact Us”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 8 phone links and 0 email links.
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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
35 other companies contacted
Loading the homepage contacts 35 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 dsldhomes.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on dsldhomes.com, including 20 speed issues, 1 SEO issue and 1 conversion gap. 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.