Website review, no card needed

addmangroup.com logo

addmangroup.com website review

Visit site (opens in a new tab)Reviewed 31 October 202632 issues · 77 checks

This review found 32 issues worth fixing on addmangroup.com, 15 of them high impact, across 77 checks. The most urgent: improve image delivery. 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
5.7 s2.6 sMay 9Oct 243.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.2 s
May 16, 20263.3 s
May 23, 20263.6 s
May 30, 20263.9 s
Jun 6, 20263.8 s
Jun 13, 20264.0 s
Jun 20, 20263.8 s
Jun 27, 20263.5 s
Jul 4, 20263.5 s
Jul 11, 20263.6 s
Jul 18, 20263.8 s
Jul 25, 20264.3 s
Aug 1, 20265.0 s
Aug 8, 20265.2 s
Aug 15, 20265.3 s
Aug 22, 20265.2 s
Aug 29, 20265.0 s
Sep 5, 20264.6 s
Sep 12, 20263.4 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20263.1 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Oct 24, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
112 ms84 msMay 9Oct 2496 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026104 ms
May 16, 2026105 ms
May 23, 202697 ms
May 30, 202689 ms
Jun 6, 202689 ms
Jun 13, 202689 ms
Jun 20, 202695 ms
Jun 27, 202698 ms
Jul 4, 202696 ms
Jul 11, 202688 ms
Jul 18, 202694 ms
Jul 25, 202694 ms
Aug 1, 202696 ms
Aug 8, 2026109 ms
Aug 15, 2026104 ms
Aug 22, 2026102 ms
Aug 29, 202699 ms
Sep 5, 202692 ms
Sep 12, 202688 ms
Sep 19, 202688 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202695 ms
Oct 17, 2026102 ms
Oct 24, 202696 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 addmangroup.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. addmangroup.com at 0.4 s0.4 s
  2. addmangroup.com at 0.8 s0.8 s
  3. addmangroup.com at 1.2 s1.2 s
  4. addmangroup.com at 1.6 s1.6 s
  5. addmangroup.com at 2.1 s2.1 s
  6. addmangroup.com at 2.5 s2.5 s
  7. addmangroup.com at 2.9 s2.9 s
  8. addmangroup.com at 3.3 s3.3 s

Speed

6 to fix65
  • Improve image delivery

    1.9 s · 1.9 MB

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

  • Use efficient cache lifetimes

    2.1 s · 740 KiB

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

  • Render-blocking requests

    2.2 s

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

  • Mobile performance score: 65

    65/100

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

  • Font display

    450 ms

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

  • Reduce unused CSS

    300 ms · 45 KiB

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

  • Reduce unused JavaScript

    150 ms · 30 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (cdn-cookieyes.com, JSDelivr CDN and Adobe TypeKit and others), adding 130 KiB and 33 ms of main-thread time.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 216 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

9 to fix67
  • 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.

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 14.7 s

    14.7 s

    Your largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies on our website to enable and improve website…”.

  • Time to Interactive: 15.2 s

    15.2 s

    The page becomes fully interactive after 15.2 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 LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Speed Index: 5.6 s

    5.6 s

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

  • 13 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

4 checks passed
  • Real-user INP: 104 ms

    104 ms

    Real visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

5 to fix18
  • Page weight: 15.6 MB in 82 requests

    15.6 MB

    Your homepage downloads 15.6 MB in 82 requests on a phone: media 12.1 MB (1), images 2.6 MB (22) and fonts 488 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    ADDMAN_Niobium_eBook_mockup3_v2-copy.jpg weighs 1.0 MB. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    1.4 MB

    6 images are downloaded at several times the size a phone draws them, for example ADDMAN_Niobium_eBook_mockup3_v2-copy.jpg at 2,200 px wide, shown at 312 px. Resized copies would save about 1.4 MB.

  • 10 images in older formats

    10 images (2.3 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.

  • 11 images below the first screen load straight away

    11 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.4 g of CO₂ per visit

    4.43 g

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

Accessibility

5 to fixGoogle 8693
  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 7 images without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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

3 to fixGoogle 7788
  • 3 H1 headlines

    There are 3 <h1> headlines (“Services”, “Delivering solutions, no matter the challenge.” and “How Additive Manufacturing Helps Farm Robots Make…”). One clear main headline is easier for people and search engines.

  • Meta description is long (279 characters)

    Your meta description is 279 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 8 links with vague text

    8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 160 internal links, 10 external

    The homepage links to 160 pages on addmangroup.com and 10 external pages.

6 checks passed
  • Title: 41 characters

    Your title is a healthy 41 characters: “ADDMAN | Advanced Manufacturing Solutions”.

  • Canonical URL set

    The canonical URL is https://www.addmangroup.com/.

  • Structured data in place

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.addmangroup.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.addmangroup.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 (987 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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

3 to fixGoogle 9271
  • 2 broken images

    2 images failed to load on a phone, for example https://www.addmangroup.com/.

  • 5 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “n.ready is not a function”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 713 words of copy

    The homepage carries about 713 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REQUEST A QUOTE” and “POLYMER INSTANT QUOTE”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Learn More About Castheon Hypersonics”, “Contact Us” and “REQUEST A QUOTE”.

  • 1 short form

    A short form (5 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and HubSpot.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads HubSpot (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 11 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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 addmangroup.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
Hosting
Involta

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on addmangroup.com, including 15 speed issues, 3 SEO issues and 1 conversion gap. 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