Website review, no card needed

mac-group.com logo

mac-group.com website review

Visit site (opens in a new tab)Reviewed 25 October 202629 issues · 75 checks

This review found 29 issues worth fixing on mac-group.com, 8 of them high impact, across 75 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.5 sMay 9Oct 31.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.6 s
Sep 12, 20262.1 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20261.9 s

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of mac-group.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mac-group.com at 0.4 s0.4 s
  2. mac-group.com at 0.8 s0.8 s
  3. mac-group.com at 1.1 s1.1 s
  4. mac-group.com at 1.5 s1.5 s
  5. mac-group.com at 1.9 s1.9 s
  6. mac-group.com at 2.3 s2.3 s
  7. mac-group.com at 2.6 s2.6 s
  8. mac-group.com at 3.0 s3.0 s

Speed

5 to fix66
  • Render-blocking requests

    2.4 s

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

  • Use efficient cache lifetimes

    1.5 s · 281 KiB

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

  • Mobile performance score: 66

    66/100

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

  • Reduce unused JavaScript

    750 ms · 186 KiB

    About 186 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 44 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Facebook, Google Tag Manager and Google Analytics and others), adding 462 KiB and 312 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Improve image delivery

    131 KiB

    7 images could be 131 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    12 KiB

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

  • Chained critical requests

    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 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 411 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 9.6 s

    9.6 s

    Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Specialist Interiors & Construction Partner”.

  • Time to Interactive: 9.6 s

    9.6 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • 33 images without width and height

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

  • Speed Index: 4.5 s

    4.5 s

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

4 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Total Blocking Time: 143 ms

    143 ms

    Scripts block the page for only 143 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.003

    0.003

    The layout barely moves while loading (CLS 0.003, good is under 0.1).

Images and page weight

1 to fix90
  • 1 image far larger than shown

    43 KiB

    1 image is downloaded at several times the size a phone draws it, for example autodesk-logo.png at 900 px wide, shown at 200 px. Resized copies would save about 43 KiB.

  • About 0.4 g of CO₂ per visit

    0.43 g

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

3 checks passed
  • Page weight: 1.5 MB in 77 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 77 requests on a phone: scripts 671 KiB (26), images 560 KiB (25) and fonts 192 KiB (3). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8894
  • 11 text elements with low contrast

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

  • 32 images without alt text

    32 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (11 elements)

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

  • 23 links without text

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

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7780
  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “mac-group | Your Specialist Construction, Interiors and Modular Partner”.

  • 18 H1 headlines

    There are 18 <h1> headlines (“Your Specialist Interiors & Construction Partner”, “"From the initial kick-off meeting, we were satis…” and ““Thanks for delivering the project so successfull…”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • No favicon declared

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 1 link with vague text

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

  • 81 internal links, 10 external

    The homepage links to 81 pages on mac-group.com and 10 external pages.

5 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “mac-group; Your specialist construction, interiors and modular partner. Contractor, Refurbishment, Renovation, Commerci…”.

  • Canonical URL set

    The canonical URL is https://www.mac-group.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.mac-group.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.mac-group.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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,563 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 4 pages share 2 titles

    https://www.mac-group.com/who-we-are/leadership-team and https://www.mac-group.com/who-we-are/leadership-team-2 all use the title “mac-group | Leadership Team”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://www.mac-group.com/who-we-are/leadership-team and https://www.mac-group.com/who-we-are/leadership-team-2 use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.mac-group.com/who-we-are/leadership-team, whose canonical is https://www.mac-group.com/who-we-are/leadership-team-2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No risk reducer

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

  • About 1,216 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “Get in Touch”.

  • 3 short forms

    3 short forms (4 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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.

  • 13 cookies set on arrival

    13

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

  • No consent tool detected

    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.

  • 8 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mac-group.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on mac-group.com, including 12 speed issues and 6 SEO issues. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25
mac-group.com website review: scores and fixes