clacorp.com website review

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

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

About 64 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.

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

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

1 long task block the main thread while loading, the longest for 75 ms. During a long task the page ignores taps.

2 third-party services load with your homepage (Google Maps and Google Fonts), adding 122 KiB and 62 ms of main-thread time.

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

1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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 KiB could be saved by minifying CSS.

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

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LENDING THE WAY OUR CUSTOMERS NEED IT TODAY”. Most of its time is element render delay (1.4 s).

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

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

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

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.

https://clacorp.com/?file=media.png weighs 3.2 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.6 MB in 23 requests on a phone: images 3.3 MB (2), HTML 127 KiB (1) and scripts 103 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image (3.2 MB) is 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 124.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Your meta description is only 32 characters: “Community Loans of America, Inc.”. 70 to 160 characters is enough to sell the click.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 23 pages on clacorp.com and 0 external pages.

Your Organization JSON-LD is missing 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.

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.

/, /about-us and /contact-us all use the title “Community Loans of America, Inc.”. Search engines can't tell which page to show for a search, so each competes with the others.

/about-us, /contact-us and /news use the same meta description. A description written for each page earns more clicks.

We fetched 5 pages linked from your homepage and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Applying inline style violates the following Content Security Policy directive 'default-src * data:'. Either the 'unsaf…”.

Chrome logged issues while loading the page (“Content security policy”).

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

clacorp.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

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

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage has only about 80 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Opening the homepage sets 2 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.