Website review, no card needed

eammosca.com logo

eammosca.com website review

Visit site (opens in a new tab)Reviewed 30 October 202644 issues · 92 checks

This review found 44 issues worth fixing on eammosca.com, 19 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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.5 sMay 9Oct 244.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.9 s
May 16, 20263.8 s
May 23, 20263.8 s
May 30, 20263.6 s
Jun 6, 20263.6 s
Jun 13, 20263.7 s
Jun 20, 20263.6 s
Jun 27, 20263.7 s
Jul 4, 20263.8 s
Jul 11, 20263.8 s
Jul 18, 20263.8 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20264.2 s
Aug 15, 20264.2 s
Aug 22, 20264.2 s
Aug 29, 20264.1 s
Sep 5, 20263.8 s
Sep 12, 20263.9 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20264.1 s
Oct 10, 20263.9 s
Oct 17, 20264.0 s
Oct 24, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
205 ms125 msMay 9Oct 24170 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026167 ms
May 16, 2026182 ms
May 23, 2026173 ms
May 30, 2026195 ms
Jun 6, 2026177 ms
Jun 13, 2026194 ms
Jun 20, 2026196 ms
Jun 27, 2026177 ms
Jul 4, 2026193 ms
Jul 11, 2026171 ms
Jul 18, 2026171 ms
Jul 25, 2026168 ms
Aug 1, 2026171 ms
Aug 8, 2026170 ms
Aug 15, 2026173 ms
Aug 22, 2026168 ms
Aug 29, 2026161 ms
Sep 5, 2026154 ms
Sep 12, 2026145 ms
Sep 19, 2026154 ms
Sep 26, 2026134 ms
Oct 3, 2026145 ms
Oct 10, 2026159 ms
Oct 17, 2026163 ms
Oct 24, 2026170 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 eammosca.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eammosca.com at 0.7 s0.7 s
  2. eammosca.com at 1.4 s1.4 s
  3. eammosca.com at 2.1 s2.1 s
  4. eammosca.com at 2.8 s2.8 s
  5. eammosca.com at 3.5 s3.5 s
  6. eammosca.com at 4.2 s4.2 s
  7. eammosca.com at 4.9 s4.9 s
  8. eammosca.com at 5.6 s5.6 s

Speed

12 to fix55
  • Reduce unused JavaScript

    2.4 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Render-blocking requests

    1.5 s

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

  • Improve image delivery

    1.1 s · 224 KiB

    1 image could be 224 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google CDN and Cookiebot and others), adding 2.0 MB and 928 ms of main-thread time.

  • Mobile performance score: 55

    55/100

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

  • Use efficient cache lifetimes

    850 ms · 98 KiB

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

  • Reduce unused CSS

    600 ms · 300 KiB

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

  • YouTube adds 439 ms

    439 ms

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

  • Google CDN adds 274 ms

    274 ms

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

  • Legacy JavaScript

    297 KiB

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

  • Main-thread work: 2.6 s

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

  • 1,928 HTML elements

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

  • 9 long tasks on the main thread

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

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

1 checks passed
  • Server response: 36 ms

    36 ms

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

Core Web Vitals

11 to fix33
  • 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 LCP: 4.0 s

    4.0 s

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

  • Real-user CLS: 0.33

    0.33

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 2.5 s

    2.5 s

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

  • Largest Contentful Paint: 8.4 s

    8.4 s

    Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website stores first-party and third-party cookies on …”.

  • Time to Interactive: 17.7 s

    17.7 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Total Blocking Time: 297 ms

    297 ms

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

  • 11 images without width and height

    11 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 167 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +6%

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

2 checks passed
  • Real-user INP: 167 ms

    167 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 4.0 MB in 88 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 88 requests on a phone: scripts 2.0 MB (26), images 970 KiB (40) and other files 351 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    27 KiB

    2 images are downloaded at several times the size a phone draws them, for example 1717669709276~-~media--3b371b46--query.b152035d.webp at 1,280 px wide, shown at 390 px. Resized copies would save about 27 KiB.

  • 4 images in older formats

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

  • About 1.1 g of CO₂ per visit

    1.14 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 137.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 load when needed

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

Accessibility

11 to fixGoogle 8086
  • Unlabelled dropdowns

    2 dropdowns have no label.

  • 16 text elements with low contrast

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

  • ARIA input fields must have an accessible name (2 elements)

    ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

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

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

  • Headings should not be empty (17 elements)

    Headings should not be empty: 17 elements on the page fail this check, rated minor by axe-core.

  • 5 form fields without a label

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

  • 2 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 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 X (Twitter) card tag

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

  • 86 internal links, 3 external

    The homepage links to 86 pages on eammosca.com and 3 external pages.

6 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Reliable packaging solutions from MOSCA for all industries optimise processes, save costs and protect the environment! …”.

  • One H1 headline

    Your main headline reads: “End-of-line Packaging Solutions”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “High Quality Strapping Machines & Strapping Material | MOSCA”.

  • Canonical URL set

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

  • 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.eammosca.com/sitemap.xml.

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://www.eammosca.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

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

  • Text is in the HTML

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

Other pages

1 to fix98
  • 4 pages share a meta description

    https://www.eammosca.com/career, https://www.eammosca.com/success_stories, https://www.eammosca.com/downloads and https://www.eammosca.com/company/events use the same meta description. A description written for each page earns more clicks.

  • 7 pages slow to respond

    https://www.eammosca.com/news, https://www.eammosca.com/success_stories, https://www.eammosca.com/downloads, https://www.eammosca.com/company/events, https://www.eammosca.com/products/machines and https://www.eammosca.com/products/machines/strappingmachines 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 54 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

1 to fixGoogle 9293
  • 5 small tap targets

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

  • Browser-reported issues

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

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

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

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 285 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: “Contact”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Order Strap”, “Schedule Training” and “Order Parts”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 1 cookie set on arrival

    1

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

  • 17 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

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

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on eammosca.com, including 23 speed issues, 2 SEO issues and 3 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