Website review, no card needed

teichert.com logo

teichert.com website review

Visit site (opens in a new tab)Reviewed 29 October 202633 issues · 79 checks

This review found 33 issues worth fixing on teichert.com, 14 of them high impact, across 79 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.2 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.5 s
Jun 6, 20261.6 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.6 s
Jul 18, 20261.5 s
Jul 25, 20261.6 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.4 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.8 s
Oct 17, 20262.1 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
83 ms66 msMay 9Oct 2469 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202672 ms
May 16, 202676 ms
May 23, 202679 ms
May 30, 202681 ms
Jun 6, 202680 ms
Jun 13, 202680 ms
Jun 20, 202676 ms
Jun 27, 202673 ms
Jul 4, 202676 ms
Jul 11, 202674 ms
Jul 18, 202679 ms
Jul 25, 202679 ms
Aug 1, 202678 ms
Aug 8, 202678 ms
Aug 15, 202673 ms
Aug 22, 202673 ms
Aug 29, 202671 ms
Sep 5, 202674 ms
Sep 12, 202676 ms
Sep 19, 202676 ms
Sep 26, 202671 ms
Oct 3, 202671 ms
Oct 10, 202668 ms
Oct 17, 202669 ms
Oct 24, 202669 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

Full-page screenshot of teichert.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. teichert.com at 0.5 s0.5 s
  2. teichert.com at 1.0 s1.0 s
  3. teichert.com at 1.5 s1.5 s
  4. teichert.com at 2.0 s2.0 s
  5. teichert.com at 2.5 s2.5 s
  6. teichert.com at 3.0 s3.0 s
  7. teichert.com at 3.5 s3.5 s
  8. teichert.com at 4.0 s4.0 s

Speed

5 to fix56
  • Render-blocking requests

    3.3 s

    34 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.

  • Improve image delivery

    950 ms · 6.0 MB

    14 images could be 6.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    450 ms · 59 KiB

    About 59 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 63 KiB

    5 files are served with short cache lifetimes, so returning visitors download them again (63 KiB).

  • 3 third-party services on the page

    3 third-party services load with your homepage (Usercentrics CMP, Unpkg and Adobe TypeKit), adding 334 KiB and 206 ms of main-thread time.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Reduce unused CSS

    14 KiB

    About 14 KiB of CSS is downloaded but never applied on this page.

  • 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: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 366 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • 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.

  • Real-user LCP: 4.1 s

    4.1 s

    Real visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Largest Contentful Paint: 38.7 s

    38.7 s

    Your largest element takes 38.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “From infrastructure and materials to restoration, energy, a…”.

  • Speed Index: 16.0 s

    16.0 s

    Visually, the page fills in at 16.0 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 41.6 s

    41.6 s

    The page becomes fully interactive after 41.6 s. Good is under 3.8 s.

  • First Contentful Paint: 4.9 s

    4.9 s

    The first text or image appears after 4.9 s on a phone. Good is under 1.8 s.

  • Largest content (LCP) got 60% slower for real visitors

    +60%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 21 images without width and height

    21 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -7%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 72 ms to 69 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user INP: 59 ms

    59 ms

    Real visitors wait 59 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 652 ms

    652 ms

    Real visitors wait 652 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix60
  • Page weight: 12.8 MB in 130 requests

    12.8 MB

    Your homepage downloads 12.8 MB in 130 requests on a phone: images 12.0 MB (40), scripts 485 KiB (45) and fonts 153 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    69 KiB

    2 images are downloaded at several times the size a phone draws them, for example Mathews-Readymix-LLC_Stack_Primary-Black-ATFC.svg at 1,770 px wide, shown at 115 px. Resized copies would save about 69 KiB.

  • 3 images below the first screen load straight away

    3 images further down the page (146 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.6 g of CO₂ per visit

    3.62 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.62 g of CO₂e: 434.1 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

4 to fixGoogle 8893
  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 17 images without alt text

    17 images have no alt text, which hurts accessibility and image search.

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (5 elements).

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8573
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (8 characters)

    Your title is only 8 characters: “Teichert”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (164 characters)

    Your meta description is 164 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.

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 84 internal links, 4 external

    The homepage links to 84 pages on teichert.com and 4 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://teichert.com/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • 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://teichert.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (1 of 6 facts)

    Your Organization JSON-LD is missing url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://teichert.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 (712 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://teichert.com/subcontractors, https://teichert.com/project/intuit-dome, https://teichert.com/project/hallwood-restoration, https://teichert.com/project/tuolumne-river-restoration and https://teichert.com/project/middle-mile-broadband-initiative have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://teichert.com/locations, whose canonical is https://teichert.com/company/locations. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page with very little text

    https://teichert.com/locations 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 42 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.

  • 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

2 to fixGoogle 9687
  • 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.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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.

  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 603 words of copy

    The homepage carries about 603 words of visible text.

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “Learn More”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 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.

2 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) loads with the page.

  • 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 teichert.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
Analytics
Google Analytics
Hosting
Cloudflare

Company

Employees
2,947
Founded
1887
Headquarters
Sacramento

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on teichert.com, including 13 speed issues, 5 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25