Website review, no card needed
schwagerdavis.com website review
Visit site (opens in a new tab)Reviewed 24 October 202632 issues · 78 checks
This review found 32 issues worth fixing on schwagerdavis.com, 11 of them high impact, across 78 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
64DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
2.5 s
5.0 s
7.5 s
10.0 s
12.5 s
15.0 s
17.5 s
20.1 s
Speed
Improve image delivery
2.5 s · 1.3 MB8 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 68). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 950 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
300 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
WordPress adds 0 ms
0 msWordPress costs a phone 0 ms of main-thread work and 453 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.
Reduce unused JavaScript
150 ms · 141 KiBAbout 141 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 55 KiBAbout 55 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 72 ms. During a long task the page ignores taps.
4 third-party services on the page
4 third-party services load with your homepage (Adobe TypeKit, Google Fonts and wpsitekeep.com and others), adding 665 KiB and 3 ms of main-thread time.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 68 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.
Use efficient cache lifetimes
8 KiB3 files are served with short cache lifetimes, so returning visitors download them again (8 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 126 ms
126 msYour server sent the HTML in 126 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 15.3 s
15.3 sVisually, the page fills in at 15.3 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “stay_cables”. Most of its time is resource load delay (5.7 s).
Cumulative Layout Shift: 0.484
0.484The layout shifts by 0.484 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 8.3 s
8.3 sThe page becomes fully interactive after 8.3 s. Good is under 3.8 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.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.
1 checks passed
Total Blocking Time: 20 ms
20 msScripts block the page for only 20 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.9 MB in 84 requests
3.9 MBYour homepage downloads 3.9 MB in 84 requests on a phone: images 3.1 MB (36), scripts 337 KiB (16) and fonts 323 KiB (10). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (982 KiB) 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 1.1 g of CO₂ per visit
1.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.10 g of CO₂e: 132.5 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
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
18 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 18 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “: : Schwager Davis Inc. : : Construction | Post-Tensioning | Bridge | Transit | O&M”.
11 links crawlers can't follow
11 links have no real href, so search engines can't follow them.
42 internal links, 10 external
The homepage links to 42 pages on schwagerdavis.com and 10 external pages.
6 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “A diversified design-build engineering contractor specializing in Post-Tensioning, Bridge Construction, Transportation …”.
Canonical URL set
The canonical URL is https://schwagerdavis.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://schwagerdavis.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://schwagerdavis.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (556 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://schwagerdavis.com/project/sdi-a-top-600-specialty-contractor, https://schwagerdavis.com/project/schuyler-heim-fender-dropschuyler-heim-fender-dropschuyler-heim-fender-drop, https://schwagerdavis.com/project/maui-tram-om and https://schwagerdavis.com/project/hillcrest-water-storage-tanks have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://schwagerdavis.com/contact and https://schwagerdavis.com/project/i-90-floating-bridge-retrofit have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://schwagerdavis.com/contact, https://schwagerdavis.com/project/maui-tram-om, https://schwagerdavis.com/project/san-onofre-nuclear-decommissioning, https://schwagerdavis.com/project/hillcrest-water-storage-tanks, https://schwagerdavis.com/project/los-angeles-nfl-stadium and https://schwagerdavis.com/project/ca-high-speed-rail and 1 other have 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.
12 pages slow to respond
https://schwagerdavis.com/divisions/post-tensioning-stay-cables, https://schwagerdavis.com/divisions/structural-retrofit, https://schwagerdavis.com/divisions/transit, https://schwagerdavis.com/about, https://schwagerdavis.com/projectsnews and https://schwagerdavis.com/contact and 6 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 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.
Titles are unique
Every page we checked has its own title.
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
1 broken image
1 image failed to load on a phone, for example https://sdi.wpsitekeep.com/new/wp-content/uploads/2016/09/cropped-sdi_logo_rgb.png.
4 small tap targets
4 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 distorted images
5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
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.
Only about 245 words
The homepage has only about 245 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
5 other companies contacted
Loading the homepage contacts 5 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 schwagerdavis.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
- WordPress
- Framework
- jQuery
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on schwagerdavis.com, including 11 speed issues, 3 SEO issues and 5 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.