Website review, no card needed
smithdray.com website review
Visit site (opens in a new tab)Reviewed 25 October 202623 issues · 66 checks
This review found 23 issues worth fixing on smithdray.com, 6 of them high impact, across 66 checks. The most urgent: page weight: 12.5 MB in 55 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
80BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.1 s
1.7 s
2.3 s
2.8 s
3.4 s
3.9 s
4.5 s
Speed
Improve image delivery
5.8 MB8 images could be 5.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 65
65/100Your mobile performance score is 65 (desktop: 82). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 44 KiBAbout 44 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Legacy JavaScript
150 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 132 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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 698 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 20.9 s
20.9 sYour largest element takes 20.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and similar technologies for analytics, adve…”.
Speed Index: 16.2 s
16.2 sVisually, the page fills in at 16.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 22.6 s
22.6 sThe page becomes fully interactive after 22.6 s. Good is under 3.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 79 ms
79 msScripts block the page for only 79 ms while loading. Good is under 200 ms.
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: 12.5 MB in 55 requests
12.5 MBYour homepage downloads 12.5 MB in 55 requests on a phone: images 6.6 MB (14), media 5.4 MB (2) and scripts 422 KiB (16). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 6.1 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
2.0 MB3 images are downloaded at several times the size a phone draws them, for example military-and-pcs.jpg at 6,040 px wide, shown at 358 px. Resized copies would save about 2.0 MB.
10 images below the first screen load straight away
10 images further down the page (6.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
8 images in older formats
8 images (6.4 MB) are 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.6 g of CO₂ per visit
3.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.55 g of CO₂e: 426.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
1 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Moving Companies in South Carolina,North Carolina | SDL - Est. 1888”.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (171 characters)
Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
49 internal links, 8 external
The homepage links to 49 pages on smithdray.com and 8 external pages.
4 checks passed
One H1 headline
Your main headline reads: “MovingResidentialResidential”.
Structured data in place
Structured data found: Organization.
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.smithdray.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.smithdray.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (786 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share a title
https://www.smithdray.com/blog, https://www.smithdray.com/services, https://www.smithdray.com/international-moving, https://www.smithdray.com/storage-service, https://www.smithdray.com/logistics and https://www.smithdray.com/trans-load all use the title “Smith Dray Line | Premier Moving & Storage Services in SC & NC”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages share a meta description
https://www.smithdray.com/blog, https://www.smithdray.com/services, https://www.smithdray.com/international-moving, https://www.smithdray.com/storage-service, https://www.smithdray.com/logistics and https://www.smithdray.com/trans-load use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.smithdray.com/blog has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.smithdray.com/blog 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
5 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.
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
2 JavaScript errors while loading
2 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.
2 checks passed
Tap targets are thumb-sized
11 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 818 words of copy
The homepage carries about 818 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get a Quote”.
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “Get a Quote” and “Prefer a formal quote”.
Social proof on the page
Social proof on the homepage: a star rating, 1 trust badge and “44+ reviews”.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
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.
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 smithdray.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
- Next.js
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on smithdray.com, including 7 speed issues, 4 SEO issues and 2 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.