lausgroup.com.ph website review

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

About 2.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 14.4 s faster on a phone.

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

175 KiB could be saved by minifying CSS.

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

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

About 2.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and jQuery CDN and others), adding 3.6 MB and 1.4 s of main-thread time.

Google CDN costs a phone 759 ms of main-thread work and 2.2 MB 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.

371 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 286 ms of main-thread work and 557 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.

The page has 2,348 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google Maps costs a phone 97 ms of main-thread work and 392 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.

3 images could be 125 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need.

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.

Real visitors wait 7.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element takes 27.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

Your homepage downloads 12.2 MB in 177 requests on a phone: scripts 5.1 MB (78), stylesheets 3.1 MB (43) and images 2.2 MB (25). Under 2 MB keeps phones on slow connections fast.

lgc-red-slogan-Banner1-768x67.jpg 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).

4 images (729 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.

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

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

All page content should be contained by landmarks: 17 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.

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.

27 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 22 characters: “LausGroup of Companies”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

4 links have no real href, so search engines can't follow them.

The homepage links to 109 pages on lausgroup.com.ph and 18 external pages.

Your Organization JSON-LD is missing 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 https://lausgroup.com.ph/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://lausgroup.com.ph/company-profile, https://lausgroup.com.ph/mission-vision, https://lausgroup.com.ph/about-the-founder, https://lausgroup.com.ph/baic, https://lausgroup.com.ph/bmw-pampanga-premier-cars and https://lausgroup.com.ph/carmix-pampanga and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://lausgroup.com.ph/company-profile, https://lausgroup.com.ph/mission-vision, https://lausgroup.com.ph/about-the-founder, https://lausgroup.com.ph/baic, https://lausgroup.com.ph/bmw-pampanga-premier-cars and https://lausgroup.com.ph/carmix-pampanga and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://lausgroup.com.ph/carmix-pampanga, https://lausgroup.com.ph/ford and https://lausgroup.com.ph/foton took over 3 s to send their HTML from our server.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 25 fields (9 required). Every extra field lowers completion.

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 148 words of visible text; thin pages give Google and first-time buyers little to go on.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.