cargas.com website review

About 652 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

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

15 images could be 628 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

About 199 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (hsappstatic.net, clym-widget.net and clym-sdk.net and others), adding 1.7 MB and 1.4 s of main-thread time.

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

hsappstatic.net costs a phone 491 ms of main-thread work and 702 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.

clym-widget.net costs a phone 478 ms of main-thread work and 506 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.

A phone's processor spends 4.0 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

9 long tasks block the main thread while loading, the longest for 320 ms. During a long task the page ignores taps.

Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

Your largest element takes 21.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Software to Power Your Business When you use technology eff…”.

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

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

The layout shifts by 0.292 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

Your homepage downloads 3.5 MB in 189 requests on a phone: scripts 2.0 MB (121), images 922 KiB (28) and stylesheets 263 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

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

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There are 3 <h1> headlines (“Software to Power Your Business”, “Make It Easier to Get More Done” and “See Your Success”). One clear main headline is easier for people and search engines.

Your meta description is 227 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 91 pages on cargas.com and 15 external pages.

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

/software/microsoft/power-bi is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/careers, /events, /learning-center, /software/erp, /software/acumatica and /software/microsoft/dynamics-365-business-central and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

2 links go through two or more redirects, for example https://support.cargas.com/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

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

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

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 353 words of visible text.

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.

Before a visitor clicks anything, the page loads Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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