Website review, no card needed
kreit.net website review
Visit site (opens in a new tab)Reviewed 5 November 202630 issues · 52 checks
This review found 30 issues worth fixing on kreit.net, 9 of them high impact, across 52 checks. The most urgent: page weight: 4.2 MB in 19 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
68DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
4.2 MB18 files are served with short cache lifetimes, so returning visitors download them again (4.2 MB).
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 1.4 s. During a long task the page ignores taps.
Reduce unused JavaScript
1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
735 KiB4 images could be 735 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 500 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
250 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.
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.
1 checks passed
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 18.3 s
18.3 sThe page becomes fully interactive after 18.3 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.722
0.722The layout shifts by 0.722 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 697 ms
697 msScripts block taps and scrolling for 697 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.9 s
4.9 sVisually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.
5 images without width and height
5 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.
2 checks passed
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.1 s
1.1 sYour largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Redefining Excellence in Plumbing & HVAC.”.
Images and page weight
Page weight: 4.2 MB in 19 requests
4.2 MBYour homepage downloads 4.2 MB in 19 requests on a phone: images 2.3 MB (16), scripts 1.9 MB (1) and stylesheets 7 KiB (1). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (629 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.
3 images below the first screen load straight away
3 images further down the page (583 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images far larger than shown
231 KiB3 images are downloaded at several times the size a phone draws them, for example facility-hq.0bd63542dd7019a839d6.jpg at 1,567 px wide, shown at 350 px. Resized copies would save about 231 KiB.
About 1.2 g of CO₂ per visit
1.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.19 g of CO₂e: 142.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Heading levels should only increase by one (3 elements)
Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 2 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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 (163 characters)
Your meta description is 163 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.
No XML sitemap
No XML sitemap at https://kreit.net/sitemap.xml, so Google discovers your pages only by following links.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
2 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Kreit Mechanical Associates — Plumbing & HVAC Since 1959”.
robots.txt in place
robots.txt is in place.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 1,609 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://kreit.net/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.
1 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.
Best practices
Missing source maps
Large scripts ship without source maps.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,609 words of copy
The homepage carries about 1,609 words of visible text.
1 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “START A CONVERSATION”.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies (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.
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 kreit.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Azure
Company
- Employees
- 12
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on kreit.net, including 11 speed issues, 7 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.