lasacoassurance.com website review

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

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

25 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

66 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

Your mobile performance score is 63 (desktop: 62). Pages that score under 90 lose visitors before the first paint.

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

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

3 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Google Analytics), adding 189 KiB and 178 ms of main-thread time.

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

8 KiB could be saved by minifying CSS.

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.

Your largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Buy Insurance in a Minute Motor Insurance Marine Insurance …”.

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

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

Scripts block taps and scrolling for 265 ms in total while the page loads. Good is under 200 ms.

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

5 images 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.

Your homepage downloads 16.9 MB in 80 requests on a phone: images 16.3 MB (46), scripts 319 KiB (14) and fonts 162 KiB (1). Under 2 MB keeps phones on slow connections fast.

5 images weigh 10.8 MB together. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example news-42.JPG at 6,000 px wide, shown at 366 px. Resized copies would save about 9.2 MB.

18 images (13.4 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.

19 images further down the page (13.4 MB) 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 4.79 g of CO₂e: 574.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 35 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 69 characters: “Insurance is a nice and clean responsive business related website CMS”. 70 to 160 characters is enough to sell the click.

There are 7 <h1> headlines (“Buy Insurance in a Minute”, “Lasaco Care” and “Motor and Car Insurance”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No XML sitemap at https://lasacoassurance.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at lasacoassurance.com/robots.txt, the first file search crawlers ask for.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 106 pages on lasacoassurance.com and 16 external pages.

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.

There is no https://lasacoassurance.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.

https://lasacoassurance.com/page/our-culture, https://lasacoassurance.com/page/vacancies, https://lasacoassurance.com/page/apply, https://lasacoassurance.com/page/isms-policy, https://lasacoassurance.com/page/subsidiaries and https://lasacoassurance.com/service/fire-insurance and 5 others have no <title>, so Google invents the link text in results.

https://lasacoassurance.com/page/about-us, https://lasacoassurance.com/page/board-of-directors, https://lasacoassurance.com/page/management-team, https://lasacoassurance.com/page/our-culture, https://lasacoassurance.com/page/vacancies and https://lasacoassurance.com/page/apply and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://lasacoassurance.com/page/board-of-directors, https://lasacoassurance.com/page/management-team, https://lasacoassurance.com/page/our-culture, https://lasacoassurance.com/page/vacancies, https://lasacoassurance.com/page/apply and https://lasacoassurance.com/page/quality-policy and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

9 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 errors were logged to the browser console while the page loaded, for example “Loading the stylesheet 'https://cdn.ckeditor.com/ckeditor5/39.0.1/classic/theme/ckeditor.css' violates the following Co…”.

9 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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

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.

Your longest form asks for 8 fields (1 required). Every extra field lowers completion.

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

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

The homepage carries about 1,138 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 5 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.