Website review, no card needed

macter.com logo

macter.com website review

Visit site (opens in a new tab)Reviewed 25 October 202639 issues · 79 checks

This review found 39 issues worth fixing on macter.com, 10 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
4.3 s3.2 sMay 2Oct 173.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.3 s
May 9, 20263.5 s
May 16, 20263.6 s
May 23, 20263.7 s
May 30, 20263.7 s
Jun 6, 20263.7 s
Jun 13, 20263.6 s
Jun 20, 20263.7 s
Jun 27, 20263.8 s
Jul 4, 20263.8 s
Jul 11, 20263.8 s
Jul 18, 20263.9 s
Jul 25, 20263.8 s
Aug 1, 20263.8 s
Aug 8, 20263.9 s
Aug 15, 20263.9 s
Aug 22, 20264.0 s
Aug 29, 20263.9 s
Sep 5, 20263.8 s
Sep 12, 20263.8 s
Sep 19, 20263.9 s
Sep 26, 20264.0 s
Oct 3, 20264.0 s
Oct 10, 20264.1 s
Oct 17, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
114 ms99 msMay 2Oct 10103 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026105 ms
May 9, 2026106 ms
May 16, 2026105 ms
May 23, 2026105 ms
May 30, 2026103 ms
Jun 6, 2026101 ms
Jun 13, 2026105 ms
Jun 20, 2026106 ms
Jun 27, 2026105 ms
Jul 4, 2026104 ms
Jul 11, 2026102 ms
Jul 18, 2026103 ms
Jul 25, 2026102 ms
Aug 1, 2026103 ms
Aug 8, 2026103 ms
Aug 15, 2026103 ms
Aug 22, 2026107 ms
Aug 29, 2026110 ms
Sep 5, 2026112 ms
Sep 12, 2026110 ms
Sep 19, 2026106 ms
Sep 26, 2026103 ms
Oct 3, 2026101 ms
Oct 10, 2026103 ms

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 macter.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. macter.com at 0.9 s0.9 s
  2. macter.com at 1.7 s1.7 s
  3. macter.com at 2.6 s2.6 s
  4. macter.com at 3.4 s3.4 s
  5. macter.com at 4.3 s4.3 s
  6. macter.com at 5.2 s5.2 s
  7. macter.com at 6.0 s6.0 s
  8. macter.com at 6.9 s6.9 s

Speed

8 to fix55
  • Use efficient cache lifetimes

    3.8 s · 1.1 MB

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

  • Render-blocking requests

    2.6 s

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

  • Improve image delivery

    1.6 s · 435 KiB

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

  • Mobile performance score: 55

    55/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google/Doubleclick Ads and others), adding 1.1 MB and 506 ms of main-thread time.

  • YouTube adds 495 ms

    495 ms

    YouTube costs a phone 495 ms of main-thread work and 977 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.

  • Reduce unused JavaScript

    571 KiB

    About 571 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 2.1 s

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

  • Font display

    250 ms

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

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    139 KiB

    About 139 KiB of CSS is downloaded but never applied on this page.

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

  • Forced reflow

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 32 ms

    32 ms

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

Core Web Vitals

6 to fix59
  • Speed Index: 11.1 s

    11.1 s

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

  • Time to Interactive: 13.8 s

    13.8 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “More than four decades of Pharmaceutical & Biopharmaceutica…”. Most of its time is element render delay (5.4 s).

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.173

    0.173

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

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

    +18%

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Total Blocking Time: 153 ms

    153 ms

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

Images and page weight

4 to fix67
  • Page weight: 2.2 MB in 96 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 96 requests on a phone: scripts 1.1 MB (37), images 738 KiB (10) and stylesheets 162 KiB (38). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Macter-Logo-rkb8syku9h5zdgj836flu5ru63ibqlp7ngq20somn2.png 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 in older formats

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

  • 4 images below the first screen load straight away

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

  • About 0.6 g of CO₂ per visit

    0.63 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9294
  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

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

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

  • No main landmark

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 43 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: 43 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 9258
  • No meta description

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

  • No H1 headline

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

  • Title is short (6 characters)

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

  • No structured data

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

  • No social preview image

    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

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

  • No robots.txt

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

  • No X (Twitter) card tag

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

  • 67 internal links, 11 external

    The homepage links to 67 pages on macter.com and 11 external pages.

1 checks passed
  • Canonical URL set

    The canonical URL is https://macter.com/.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 14 pages without a meta description

    https://macter.com/index.php/corporate-profile, https://macter.com/index.php/our-legacy-timeline, https://macter.com/index.php/core-management, https://macter.com/index.php/test-profile, https://macter.com/index.php/corporate-social-responsibility-csr and https://macter.com/index.php/corporate-documentary and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://macter.com/index.php/corporate-profile, https://macter.com/index.php/our-legacy-timeline, https://macter.com/index.php/core-management, https://macter.com/index.php/corporate-social-responsibility-csr, https://macter.com/index.php/corporate-documentary and https://macter.com/index.php/biologicals and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://macter.com/index.php/core-management, https://macter.com/index.php/test-profile, https://macter.com/index.php/corporate-social-responsibility-csr, https://macter.com/index.php/corporate-documentary, https://macter.com/index.php/biologicals and https://macter.com/index.php/pharmaceuticals-pharma and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7397
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 low-resolution image

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

  • Browser-reported issues

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    7 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • No call to action on the first screen

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

  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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,085 words of copy

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

2 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Investor Grievance Contact”, “Contact Us” and “Learn More”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Ads (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 1 of them by other companies (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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 macter.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on macter.com, including 14 speed issues, 7 SEO issues and 4 conversion gaps. 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