Website review, no card needed

multiplier.org logo

multiplier.org website review

Visit site (opens in a new tab)Reviewed 14 November 202633 issues · 78 checks

This review found 33 issues worth fixing on multiplier.org, 11 of them high impact, across 78 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
3.4 s2.1 sMay 30Oct 32.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.7 s
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.6 s
Aug 8, 20262.9 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.3 s
Sep 5, 20263.0 s
Sep 12, 20262.7 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
74 ms63 msJun 27Aug 2271 ms
Show as table
DateReal-visitor tap response (INP)
Jun 27, 202673 ms
Jul 4, 202673 ms
Jul 11, 202673 ms
Jul 18, 202673 ms
Jul 25, 202664 ms
Aug 1, 202665 ms
Aug 8, 202667 ms
Aug 15, 202669 ms
Aug 22, 202671 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 multiplier.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. multiplier.org at 0.4 s0.4 s
  2. multiplier.org at 0.8 s0.8 s
  3. multiplier.org at 1.2 s1.2 s
  4. multiplier.org at 1.6 s1.6 s
  5. multiplier.org at 2.0 s2.0 s
  6. multiplier.org at 2.4 s2.4 s
  7. multiplier.org at 2.9 s2.9 s
  8. multiplier.org at 3.3 s3.3 s

Speed

7 to fix66
  • Improve image delivery

    4.2 s · 1.1 MB

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

  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 66

    66/100

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

  • Use efficient cache lifetimes

    400 ms · 548 KiB

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

  • Reduce unused CSS

    450 ms · 65 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (termly.io, givebutter.com and WordPress and others), adding 1.8 MB and 246 ms of main-thread time.

  • WordPress adds 47 ms

    47 ms

    WordPress costs a phone 47 ms of main-thread work and 1.4 MB 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

    210 KiB

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

  • 2 long tasks on the main thread

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

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

  • 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, 268 ms of it running JavaScript. That is comfortably low.

  • Server response: 57 ms

    57 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 8.2 s

    8.2 s

    Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 8.2 s

    8.2 s

    The page becomes fully interactive after 8.2 s. Good is under 3.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.

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.4 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.

2 checks passed
  • Total Blocking Time: 69 ms

    69 ms

    Scripts block the page for only 69 ms while loading. 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 fix78
  • Page weight: 2.2 MB in 62 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 62 requests on a phone: images 1.6 MB (15), scripts 441 KiB (19) and stylesheets 98 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (486 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.61 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 7990
  • 8 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 1 tap target too small

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • 1 link without text

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

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 7768
  • 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 (10 characters)

    Your title is only 10 characters: “Multiplier”. 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.

  • 4 links with vague text

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

  • 24 internal links, 7 external

    The homepage links to 24 pages on multiplier.org and 7 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://multiplier.org/.

  • 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://multiplier.org/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://multiplier.org/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 (517 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 6 pages without a meta description

    https://multiplier.org/about, https://multiplier.org/news, https://multiplier.org/about/contact, https://multiplier.org/about/privacy, https://multiplier.org/about/text-messaging-terms and https://multiplier.org/about/charitable-disclosures have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://multiplier.org/about, https://multiplier.org/news, https://multiplier.org/about/contact, https://multiplier.org/about/privacy, https://multiplier.org/about/text-messaging-terms and https://multiplier.org/about/charitable-disclosures have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://multiplier.org/about/contact, https://multiplier.org/about/privacy and https://multiplier.org/about/charitable-disclosures have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 4 pages slow to respond

    https://multiplier.org/about/contact, https://multiplier.org/about/privacy, https://multiplier.org/about/text-messaging-terms and https://multiplier.org/about/charitable-disclosures took over 3 s to send their HTML from our server.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    6 pages of 13 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 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 4 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “[widgets-core] Error initializing web components NotSupportedError: Failed to execute 'define' on 'CustomElementRegistr…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

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

  • No analytics detected

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

  • No opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 366 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Multiplier”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 4 trust badges.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies, 1 of them by other companies (measured from a US location before any click).

  • 13 other companies contacted

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

2 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) 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 multiplier.org, 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
Hosting
InMotion Hosting, Inc.

Hiring

Hiring
2 open roles
Teams
Talent Acquisition (2)
Job board
bamboohr

Company

Employees
149

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on multiplier.org, including 12 speed issues, 5 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