Website review, no card needed

moodypublishers.com logo

moodypublishers.com website review

Visit site (opens in a new tab)Reviewed 20 October 202639 issues · 83 checks

This review found 39 issues worth fixing on moodypublishers.com, 11 of them high impact, across 83 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
2.7 s794 msMay 2Oct 172.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.0 s
May 9, 20261.2 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.1 s
Jul 18, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20262.4 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.2 s
Sep 26, 20262.1 s
Oct 3, 20262.3 s
Oct 10, 20262.2 s
Oct 17, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
144 ms90 msMay 2Oct 17135 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026105 ms
May 9, 2026112 ms
May 16, 202697 ms
May 23, 202697 ms
May 30, 202696 ms
Jun 6, 202697 ms
Jun 13, 2026106 ms
Jun 20, 2026105 ms
Jun 27, 2026106 ms
Jul 4, 2026113 ms
Jul 11, 2026103 ms
Jul 18, 202699 ms
Jul 25, 2026105 ms
Aug 1, 2026104 ms
Aug 8, 2026100 ms
Aug 15, 2026101 ms
Aug 22, 2026103 ms
Aug 29, 2026110 ms
Sep 5, 2026110 ms
Sep 12, 2026124 ms
Sep 19, 2026118 ms
Sep 26, 2026122 ms
Oct 3, 2026138 ms
Oct 10, 2026132 ms
Oct 17, 2026135 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 moodypublishers.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. moodypublishers.com at 0.4 s0.4 s
  2. moodypublishers.com at 0.8 s0.8 s
  3. moodypublishers.com at 1.1 s1.1 s
  4. moodypublishers.com at 1.5 s1.5 s
  5. moodypublishers.com at 1.9 s1.9 s
  6. moodypublishers.com at 2.3 s2.3 s
  7. moodypublishers.com at 2.6 s2.6 s
  8. moodypublishers.com at 3.0 s3.0 s

Speed

8 to fix63
  • Improve image delivery

    8.3 s · 2.1 MB

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

  • Use efficient cache lifetimes

    3.6 s · 679 KiB

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

  • Mobile performance score: 63

    63/100

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

  • Reduce unused JavaScript

    450 ms · 289 KiB

    About 289 KiB of JavaScript is downloaded but never used 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 (Google Tag Manager, TikTok and Cloudflare and others), adding 714 KiB and 515 ms of main-thread time.

  • Google Tag Manager adds 405 ms

    405 ms

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

  • Font display

    450 ms

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

  • Minify JavaScript

    300 ms · 48 KiB

    48 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    150 ms · 19 KiB

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

  • 10 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 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.

  • Forced reflow

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

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 762 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

11 to fix100
  • 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.

  • Largest Contentful Paint: 18.0 s

    18.0 s

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

  • Time to Interactive: 18.1 s

    18.1 s

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

  • Tap response (INP) got 23% slower for real visitors

    +23%

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

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

    +114%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Speed Index: 4.8 s

    4.8 s

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

  • Total Blocking Time: 331 ms

    331 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 2 images without width and height

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

4 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 136 ms

    136 ms

    Real visitors wait 136 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).

Images and page weight

4 to fix25
  • Page weight: 5.7 MB in 62 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 62 requests on a phone: images 4.0 MB (28), scripts 851 KiB (12) and fonts 814 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1.6 MB

    1 image is downloaded at several times the size a phone draws it, for example MoodyPublishersPreviews-5.jpg at 4,898 px wide, shown at 390 px. Resized copies would save about 1.6 MB.

  • 22 images in older formats

    22 images (4.0 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.

  • About 1.6 g of CO₂ per visit

    1.62 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.62 g of CO₂e: 194.1 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

6 to fixGoogle 7591
  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

  • 3 images without alt text

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

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

  • 4 form fields without a label

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

  • 4 links without text

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

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

3 to fixGoogle 9282
  • No H1 headline

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

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 88 internal links, 17 external

    The homepage links to 88 pages on moodypublishers.com and 17 external pages.

5 checks passed
  • Meta description: 123 characters

    Your meta description is 123 characters: “Shop for Christian books and Bible study resources, knowing your purchase helps fund the training of students for minis…”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Moody Publishers | Christian Books | Moody Publishers”.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://moodypublishers.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://moodypublishers.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (572 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 4 pages share a meta description

    https://moodypublishers.com/books, https://moodypublishers.com/bible-study, https://moodypublishers.com/kids-teens and https://moodypublishers.com/store use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://moodypublishers.com/books, https://moodypublishers.com/bible-study, https://moodypublishers.com/kids-teens and https://moodypublishers.com/store 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 25 found) and read each the way a search engine does.

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

  • 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 9693
  • 22 small tap targets

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

  • 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

2 to fix83
  • 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 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 504 words of copy

    The homepage carries about 504 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Learn More”, “Sign up here” and “Shop All”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 12 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager

Company

Founded
1894
Headquarters
Chicago

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 moodypublishers.com, including 19 speed issues, 3 SEO issues and 2 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