math.group website review

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

4 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.

About 522 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 third-party services load with your homepage (Google Tag Manager, Facebook and goadopt.io and others), adding 1.8 MB and 1.5 s of main-thread time.

Google Tag Manager costs a phone 899 ms of main-thread work and 1,024 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.

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

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

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

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

About 70 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

11 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

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

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

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

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

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

Your homepage downloads 8.7 MB in 117 requests on a phone: images 6.3 MB (35), scripts 1.9 MB (35) and fonts 431 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

7 images are downloaded at several times the size a phone draws them, for example agibank-case.png at 1,376 px wide, shown at 340 px. Resized copies would save about 284 KiB.

1 image (68 KiB) 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 2.46 g of CO₂e: 295.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

21 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: 26 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.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 29 characters: “MATH Group - Build the Beyond”. 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.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 77 pages on math.group and 31 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://math.group/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.

/ and https://math.group/es/inicio all use the title “MATH Group - Build the Beyond”. Search engines can't tell which page to show for a search, so each competes with the others.

https://math.group/contate-nos, https://math.group/es/inicio, https://math.group/verticais/beyond-banking, https://math.group/verticais/beyond-industry, https://math.group/verticais/beyond-education and https://math.group/solucoes/aumentar-receita and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://math.group/contate-nos, whose canonical is https://math.group/contato. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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 962 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (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 19 cookies (measured from a US location before any click).

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