Programmable

Website review, no card needed

mosaicjournal.com logo

mosaicjournal.com website review

Visit site (opens in a new tab)Reviewed 10 November 202618 issues · 78 checks

This review found 18 issues worth fixing on mosaicjournal.com, 3 of them high impact, across 78 checks. The most urgent: 7 text elements with low contrast. 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

Site score

96A

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
854 ms689 msMay 23Nov 7822 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026732 ms
May 30, 2026746 ms
Jun 6, 2026721 ms
Jun 13, 2026726 ms
Jun 20, 2026733 ms
Jun 27, 2026732 ms
Jul 4, 2026762 ms
Jul 11, 2026778 ms
Jul 18, 2026740 ms
Jul 25, 2026726 ms
Aug 1, 2026708 ms
Aug 8, 2026716 ms
Aug 15, 2026740 ms
Aug 22, 2026760 ms
Aug 29, 2026778 ms
Sep 5, 2026776 ms
Sep 12, 2026779 ms
Sep 19, 2026780 ms
Sep 26, 2026778 ms
Oct 3, 2026794 ms
Oct 10, 2026788 ms
Oct 17, 2026806 ms
Oct 24, 2026821 ms
Oct 31, 2026835 ms
Nov 7, 2026822 ms
Real-visitor tap response (INP)75th percentile, phones
191 ms123 msMay 23Nov 7151 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026131 ms
May 30, 2026138 ms
Jun 6, 2026145 ms
Jun 13, 2026149 ms
Jun 20, 2026150 ms
Jun 27, 2026152 ms
Jul 4, 2026154 ms
Jul 18, 2026153 ms
Jul 25, 2026152 ms
Aug 1, 2026154 ms
Aug 8, 2026160 ms
Aug 15, 2026162 ms
Aug 22, 2026162 ms
Aug 29, 2026162 ms
Sep 5, 2026159 ms
Sep 12, 2026161 ms
Sep 19, 2026163 ms
Sep 26, 2026170 ms
Oct 3, 2026177 ms
Oct 10, 2026178 ms
Oct 17, 2026183 ms
Oct 24, 2026178 ms
Oct 31, 2026163 ms
Nov 7, 2026151 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

www.mosaicjournal.com (opens in a new tab)
Full-page screenshot of mosaicjournal.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix99

  • Improve image delivery

    1,017 KiB

    14 images could be 1,017 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    350 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

  • 1,875 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (posthog.com, Hotjar and GetSiteControl and others), adding 635 KiB and 293 ms of main-thread time.

  • Reduce unused JavaScript

    195 KiB

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

  • Use efficient cache lifetimes

    143 KiB

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

  • 3 long tasks on the main thread

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

  • Duplicated JavaScript

    15 KiB

    15 KiB JavaScript is shipped twice across bundles.

  • Reduce unused CSS

    14 KiB

    About 14 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    9 KiB

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

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

3 checks passed

  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.8 s

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

  • Server response: 15 ms

    15 ms

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

Core Web Vitals

2 to fix100

  • Time to Interactive: 7.3 s

    7.3 s

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

  • 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) got 17% slower for real visitors

    +17%

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

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

    +12%

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

11 checks passed

  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.8 s

    0.8 s

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

  • Real-user INP: 121 ms

    121 ms

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 279 ms

    279 ms

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

  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.6 s

    2.6 s

    Visually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Largest Contentful Paint: 1.6 s

    1.6 s

    Your largest element renders in 1.6 s on a phone, inside Google's 2.5 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 47 ms

    47 ms

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

Images and page weight

3 to fix58

  • 8 images far larger than shown

    689 KiB

    8 images are downloaded at several times the size a phone draws them, for example 230213_Beach_Design_03006_1_3_282673aa-c5b1-460f-bc45-7b5987 at 1,522 px wide, shown at 360 px. Resized copies would save about 689 KiB.

  • Page weight: 3.6 MB in 212 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 212 requests on a phone: images 1.6 MB (23), scripts 799 KiB (61) and other files 792 KiB (103). Under 2 MB keeps phones on slow connections fast.

  • 7 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    1.03 g

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

1 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9395

  • 7 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed

  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “A Photo Journal Worthy of Your Life ✨”). One clear main headline is easier for people and search engines.

  • 2 links with vague text

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

  • 29 internal links, 8 external

    The homepage links to 29 pages on mosaicjournal.com and 8 external pages.

7 checks passed

  • Meta description: 87 characters

    Your meta description is 87 characters: “Upload a daily photo and automatically receive your prints to your home once a month 💌”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Mosaic Journal - Your Life Story in Pictures”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization 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 and points crawlers to your sitemap.

  • XML sitemap found

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

AI search readiness

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

  • llms.txt published

    The site publishes https://www.mosaicjournal.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83

  • 1 linked page hidden from search

    https://www.mosaicjournal.com/products/gift-card is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://www.mosaicjournal.com/products/gift-card, https://www.mosaicjournal.com/pages/pricing, https://www.mosaicjournal.com/pages/faqs, https://www.mosaicjournal.com/pages/contact, https://www.mosaicjournal.com/pages/privacy-policy and https://www.mosaicjournal.com/pages/terms-and-conditions have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.mosaicjournal.com/products/one-year-bundle, https://www.mosaicjournal.com/products/mosaic-journal-one-year-bundle, https://www.mosaicjournal.com/products/gift-card, https://www.mosaicjournal.com/pages/pricing, https://www.mosaicjournal.com/pages/faqs and https://www.mosaicjournal.com/pages/contact and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.mosaicjournal.com/products/one-year-bundle and https://www.mosaicjournal.com/products/mosaic-journal-one-year-bundle 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.

  • 8 internal pages checked

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

4 checks passed

  • Linked pages load

    All 8 pages we checked loaded without an error.

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

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

    12 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93

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

  • About 689 words of copy

    The homepage carries about 689 words of visible text.

6 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy a journal”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Buy a journal”, “Pricing” and “Contact Us”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 26 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel, Microsoft Clarity, Hotjar and PostHog.

  • 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 to fix

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Hotjar (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.

  • 14 cookies set on arrival

    14

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

Apps on your store

Your storefront loads 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Fontify · Awin Affiliate Marketing · Seowill Sticky Cart · Microsoft Clarity · Leaf Connect Mosaic Journal · Powerful Form Builder · Gsc Countdown Timer · Triplewhale · Crisp Live Chat Chatbot · Crisp Chatbox · Essential Icon Badge Banners · synctrack.io · getsitecontrol.com · 1clickreferralapp.com · socialsnowball.io

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
SvelteKit
E-commerce
Shopify
Analytics
Google Analytics | Hotjar | PostHog | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on mosaicjournal.com, including 5 speed issues, 2 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