Website review, no card needed
calcas.com website review
Visit site (opens in a new tab)Reviewed 31 October 202631 issues · 96 checks
This review found 31 issues worth fixing on calcas.com, 7 of them high impact, across 96 checks. The most urgent: page weight: 5.8 MB in 59 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.9 s |
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.4 s |
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.9 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 4.2 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 141 ms |
| May 16, 2026 | 141 ms |
| May 23, 2026 | 137 ms |
| May 30, 2026 | 139 ms |
| Jun 6, 2026 | 144 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 141 ms |
| Jun 27, 2026 | 140 ms |
| Jul 4, 2026 | 139 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 147 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 145 ms |
| Sep 12, 2026 | 144 ms |
| Sep 19, 2026 | 142 ms |
| Sep 26, 2026 | 138 ms |
| Oct 3, 2026 | 138 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 137 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
Speed
Improve image delivery
750 ms · 3.9 MB9 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
290 ms · 513 KiBAbout 513 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 290 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 431 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 16 KiBPolyfills for old browsers add 16 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 1.3 s of it running JavaScript. That is comfortably low.
Server response: 33 ms
33 msYour server sent the HTML in 33 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.9 s
4.9 sYour largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Teacher in class room, one of our hero's.”.
Total Blocking Time: 567 ms
567 msScripts block taps and scrolling for 567 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 4.9 s
4.9 sThe page becomes fully interactive after 4.9 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 141 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.9 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 555 ms
555 msReal visitors wait 555 ms for your server to start answering (75th percentile). Good is under 800 ms.
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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.8 MB in 59 requests
5.8 MBYour homepage downloads 5.8 MB in 59 requests on a phone: images 5.3 MB (22), scripts 397 KiB (33) and HTML 115 KiB (1). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
1.2 MB2 images are downloaded at several times the size a phone draws them, for example Guaranteed-Repair-Network.png at 1,700 px wide, shown at 380 px. Resized copies would save about 1.2 MB.
2 images in older formats
2 images (3.1 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.
3 images below the first screen load straight away
3 images further down the page (3.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
FFCarouselgrad-optimized-2.avif is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.7 g of CO₂ per visit
1.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.66 g of CO₂e: 199.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
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.
2 checks passed
Every image has alt text
All 6 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“We Do More for the People Who Give More” and “We Do More for the People Who Give More”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
2 links with vague text
2 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 incomplete here.
13 internal links, 0 external
The homepage links to 13 pages on calcas.com and 0 external pages.
5 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “California Casualty Auto and Home Insurance is designed for America's community heroes and their families. In business …”.
Title: 43 characters
Your title is a healthy 43 characters: “California Casualty Auto and Home Insurance”.
Canonical URL set
The canonical URL is https://www.calcas.com/.
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.calcas.com/sitemap.xml.
AI search readiness
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.
Some text only appears after JavaScript runs
42%The HTML your server sends has 221 of the 528 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no /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.
Other pages
2 pages share a meta description
/get-a-quote and /customer-service use the same meta description. A description written for each page earns more clicks.
1 page with very little text
/get-a-quote 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.
2 pages slow to respond
/claims and /customer-service took over 3 s to send their HTML from our server.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
7 checks passed
Linked pages load
All 7 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 7 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 7 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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.
Security and trust
No HSTS header
No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
No clickjacking protection
Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.
No X-Content-Type-Options
X-Content-Type-Options: nosniff is missing, so browsers may guess file types.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
5 checks passed
Served over HTTPS
The homepage is served over HTTPS (calcas.com).
Valid certificate (111 days left)
The certificate from DigiCert Inc · DigiCert EV RSA CA G2 verifies for calcas.com and is valid for another 111 days.
http:// redirects to https
http://calcas.com redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 8 links work
All 8 links checked from your homepage (8 internal, 0 external) answered without errors.
Domain and trust
No CAA record
calcas.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
calcas.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 30 years old
30 yearscalcas.com was registered in Mar 1996 through Network Solutions, LLC. An established domain carries more trust with email providers and search engines.
Registered until Mar 2027
calcas.com is registered until Mar 2027.
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 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 528 words of copy
The homepage carries about 528 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Learn More”, “Get a quote” and “Retrieve a saved quote >”.
1 short form
A short form (3 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be calcas.com is still delivered. Reports are on, so moving to quarantine is the next step.
Email authentication score: 75/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 ip4:208.185.229.41 ip4:208.185.229.42 ip4:208.185.229.43 ip4:208.185.229.44 ip4:208.185.229.45 ip4:216.52.6.88 i…”.
DKIM signing found
A DKIM key is published (selector “selector1”, “s1” and “s2”), so receivers can verify mail really came from you.
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.
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).
Upkeep, stack and company
Stack
- CMS
- WordPress
- Hosting
- Azure
Company
- Founded
- 1914
- Headquarters
- San Mateo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on calcas.com, including 8 speed issues, 5 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.