Website review, no card needed

numomfg.com logo

numomfg.com website review

Visit site (opens in a new tab)Reviewed 23 October 202644 issues · 82 checks

This review found 44 issues worth fixing on numomfg.com, 17 of them high impact, across 82 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
5.6 s3.2 sMay 2Oct 174.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.8 s
May 9, 20265.0 s
May 16, 20265.3 s
May 23, 20265.3 s
May 30, 20264.9 s
Jun 6, 20264.7 s
Jun 13, 20264.7 s
Jun 20, 20264.3 s
Jun 27, 20264.6 s
Jul 4, 20264.3 s
Jul 11, 20263.9 s
Jul 18, 20263.5 s
Jul 25, 20263.5 s
Aug 1, 20263.8 s
Aug 8, 20264.0 s
Aug 15, 20264.3 s
Aug 22, 20264.2 s
Aug 29, 20264.0 s
Sep 5, 20264.1 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20264.1 s
Oct 3, 20264.0 s
Oct 10, 20264.3 s
Oct 17, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
130 ms85 msMay 2Oct 17125 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026118 ms
May 9, 2026112 ms
May 16, 2026121 ms
May 23, 2026118 ms
May 30, 2026109 ms
Jun 6, 2026108 ms
Jun 13, 2026102 ms
Jun 20, 202690 ms
Jun 27, 202692 ms
Jul 4, 202695 ms
Jul 11, 202692 ms
Jul 18, 202696 ms
Jul 25, 202690 ms
Aug 1, 202695 ms
Aug 8, 202696 ms
Aug 15, 202697 ms
Aug 22, 2026101 ms
Aug 29, 202698 ms
Sep 5, 202698 ms
Sep 12, 202696 ms
Sep 19, 202699 ms
Sep 26, 2026112 ms
Oct 3, 2026112 ms
Oct 10, 2026118 ms
Oct 17, 2026125 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 numomfg.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. numomfg.com at 0.5 s0.5 s
  2. numomfg.com at 1.0 s1.0 s
  3. numomfg.com at 1.6 s1.6 s
  4. numomfg.com at 2.1 s2.1 s
  5. numomfg.com at 2.6 s2.6 s
  6. numomfg.com at 3.1 s3.1 s
  7. numomfg.com at 3.7 s3.7 s
  8. numomfg.com at 4.2 s4.2 s

Speed

14 to fix52
  • Use efficient cache lifetimes

    6.9 s · 5.4 MB

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

  • Render-blocking requests

    10.8 s

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

  • Reduce unused JavaScript

    4.6 s · 1.2 MB

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

  • Improve image delivery

    1.1 s · 3.4 MB

    15 images could be 3.4 MB 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.

  • Reduce unused CSS

    1.9 s · 250 KiB

    About 250 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Mobile performance score: 52

    52/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, hiverhq.com and Hotjar and others), adding 1.9 MB and 635 ms of main-thread time.

  • Minify JavaScript

    450 ms · 7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 13 long tasks on the main thread

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

  • hiverhq.com adds 203 ms

    203 ms

    hiverhq.com costs a phone 203 ms of main-thread work and 904 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.

  • Main-thread work: 2.7 s

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

  • Google Tag Manager adds 204 ms

    204 ms

    Google Tag Manager costs a phone 204 ms of main-thread work and 314 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.

  • Klaviyo adds 105 ms

    105 ms

    Klaviyo costs a phone 105 ms of main-thread work and 353 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 Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 307 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

    250 ms · 60 KiB

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

  • Font display

    100 ms

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

  • 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: 8 ms

    8 ms

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

Core Web Vitals

10 to fix0
  • 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.4 s

    4.4 s

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

  • Real-user CLS: 0.87

    0.87

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

  • First Contentful Paint: 11.8 s

    11.8 s

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

  • Largest Contentful Paint: 18.7 s

    18.7 s

    Your largest element takes 18.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Woman holding a bundle of colorful pens”.

  • Time to Interactive: 24.1 s

    24.1 s

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

  • Speed Index: 11.8 s

    11.8 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Total Blocking Time: 224 ms

    224 ms

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

3 checks passed
  • Real-user TTFB: 639 ms

    639 ms

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

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Cumulative Layout Shift: 0.037

    0.037

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

Images and page weight

1 to fix70
  • Page weight: 12.9 MB in 196 requests

    12.9 MB

    Your homepage downloads 12.9 MB in 196 requests on a phone: images 9.7 MB (80), scripts 2.1 MB (50) and fonts 506 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • About 3.7 g of CO₂ per visit

    3.65 g

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

3 checks passed
  • 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.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9195
  • 2 text elements with low contrast

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

  • Zoom is disabled

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

  • 5 form fields without a label

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

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

4 to fixGoogle 10082
  • Title is short (18 characters)

    Your title is only 18 characters: “Numo Manufacturing”. 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://www.numomfg.com/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 107 internal links, 5 external

    The homepage links to 107 pages on numomfg.com and 5 external pages.

4 checks passed
  • Meta description: 112 characters

    Your meta description is 112 characters: “Manufacturer and Supplier of highly customizable promotional products. Bags, Pouches, Insulators, and Drinkware.”.

  • One H1 headline

    Your main headline reads: “Cookies Notice”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • 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.numomfg.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.

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

Other pages

3 to fix75
  • 10 pages without a title

    https://www.numomfg.com/materials/leather/leather-fall-2026, https://www.numomfg.com/shapes/totes-and-bags/open-tote/local-tote, https://www.numomfg.com/participatory-promo-concepts, https://www.numomfg.com/collections/collaborations/gomi-collab, https://www.numomfg.com/materials/roperope and https://www.numomfg.com/shapes/blankets/soft-block and 4 others have no <title>, so Google invents the link text in results.

  • 13 pages without a meta description

    https://www.numomfg.com/new, https://www.numomfg.com/materials/leather/leather-fall-2026, https://www.numomfg.com/MILK-GLASS-MUG, https://www.numomfg.com/shapes/totes-and-bags/open-tote/local-tote, https://www.numomfg.com/boxd and https://www.numomfg.com/participatory-promo-concepts and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://www.numomfg.com/materials/leather/leather-fall-2026, https://www.numomfg.com/shapes/totes-and-bags/open-tote/local-tote, https://www.numomfg.com/collections/collaborations/gomi-collab, https://www.numomfg.com/materials/roperope, https://www.numomfg.com/shapes/blankets/soft-block and https://www.numomfg.com/materials/mimic and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

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

Best practices

3 to fixGoogle 7383
  • 24 small tap targets

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

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

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

4 to fix57
  • 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.

  • No social proof

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

  • No analytics detected

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

  • Only about 95 words

    The homepage has only about 95 words of visible text; thin pages give Google and first-time buyers little to go on.

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop By Event”, “Shop By Price” and “Shop By Shape”.

  • 1 short form

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 16 other companies contacted

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

Upkeep, stack and company

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on numomfg.com, including 24 speed issues, 4 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