Mobile speed report · June 25, 2026
How babybathwater.com loads on a phone
We loaded 5 of your pages on a typical phone over a normal cellular connection and recorded each one frame by frame - 52 frames in all. On a fast desktop these pages feel fine, which is exactly why what is below is easy to miss.
Captured June 25, 2026 - a snapshot of the live site that day. If the site has changed since, this report may no longer reflect it.
In plain terms, a visitor on a phone waits about 3.8s before the typical page here is usable.
How to read this. Each strip is one of your pages loading on a phone, left to right in real time. We pulled the moments that matter out of every frame we captured. Tap any frame to enlarge it.
Scrolling the homepage
/Nothing appears for the first 4.2s
The first pixels take that long to land, so the page feels stalled at the start.
▶ Press play - watch how long it sits empty before anything shows.
Frame-by-frame breakdown 7 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
Blue = the first content lands. Orange = the moment the biggest piece of the page lands. Red boxes = parts of the page that move after a visitor is already reading. A near-blank frame is a phone still showing an empty screen.
This page loads slowly - it takes over 4 seconds for content to appear and over 6 seconds for the full page to load. The heavy file size (772KB) is the main culprit, and there's also an accessibility issue that could block some users.
Events
/events/The biggest piece of the page takes 4.1s to appear
Until then a visitor on a phone is looking at a mostly empty screen.
▶ Press play - this is the 4.1s a phone visitor waits, in real time.
Frame-by-frame breakdown 11 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
Page takes 4 seconds to show main content - fairly slow, but responsive and smooth once loaded. It has 3 accessibility issues, though AI reads it very well.
About page
/about/The biggest piece of the page takes 3.6s to appear
A bit slower than the under-2.5-second mark that feels instant on a phone.
▶ Press play - this is the 3.6s a phone visitor waits, in real time.
Frame-by-frame breakdown 13 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page takes 3-4 seconds to start showing content and 5+ seconds to fully load. One major accessibility issue could block people using assistive technology, though AI assistants read it well.
Apply page
/apply/The biggest piece of the page takes 3.2s to appear
A bit slower than the under-2.5-second mark that feels instant on a phone.
▶ Press play - this is the 3.2s a phone visitor waits, in real time.
Frame-by-frame breakdown 12 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page takes 3-4 seconds to load - that's slow. It's responsive when ready, but has a serious accessibility problem that blocks people with certain disabilities.
The rest of your pages, same pattern
- Homepage / Nothing appears for the first 3.5s
Measured on June 25, 2026 on an emulated mid-range phone over the Slow-4G throttling profile Google PageSpeed uses - the conditions a real mobile visitor faces, not a developer's fast laptop. "Speed score" is the same 0-100 scale Google PageSpeed uses for mobile (90 and up is fast, under 50 is slow); "layout-shift score" is Google's CLS, where anything above 0.25 is poor.
Put together by ShakaCode.
Accessibility helps your search ranking. Search engines read the same labels, headings, and alt text that visitors with limited vision, color blindness, or keyboard navigation rely on, so these fixes help your SEO too.
A high score means most of each page is fine. But it only takes one blocking issue to turn a real customer away, so the pages below are where we'd start.
The Events page needs the most urgent attention - a form field and several links are missing readable text that keyboard and screen reader users rely on. Across all pages, some text is too light and the footer is duplicated or nested incorrectly; fixing those two patterns would improve every page at once.
How to read this. Each card explains what to change in plain language and shows a zoomed-in shot of any problem you can see on the page - red is high-impact, orange is minor. Structure issues like heading order have nothing to point at on screen, so they have no shot and are described in the text. Score is the Google Lighthouse accessibility score (0-100), the same scale Chrome and PageSpeed use.
Events
One form field has no label and five links have no readable text, so people using a screen reader or keyboard cannot tell what the field is for or where those links lead.
What to change
- Add a visible label to the unlabeled form field so people know what to type in it.
- Add readable text to the 5 links that currently have none, so it is clear where each one leads.
- Darken the light-colored text in 3 places so it is easier to read.
Homepage
Some text is too light to read easily, and the footer appears more than once in a conflicting structure, which can disorient people navigating the page with a screen reader.
What to change
- Darken the light-colored text in 3 places so it stands out against its background.
- Fix the heading order so it steps down one level at a time without skipping.
- Remove the duplicate footer and make sure it is not placed inside another page section.
Scrolling the homepage
The scrolled view of the homepage has the same issues: some text is hard to read for people with low vision, and the footer structure and heading order can disorient screen reader users.
What to change
- Darken the light-colored text in 3 places so it stands out against its background.
- Fix the heading order so it steps down one level at a time without skipping.
- Remove the duplicate footer and make sure it is not placed inside another page section.
About page
Some text is too light to read clearly, and section headings skip levels while the footer region is structured in a way that can confuse people navigating by screen reader.
What to change
- Darken the light-colored text in 3 places so it is readable against its background.
- Fix the heading order so it steps down one level at a time without skipping.
- Remove the duplicate footer region and make sure it is not nested inside another page section.
Apply page
Two pieces of text on this page are too light against their background, making them hard to read for people with low vision or in bright conditions.
What to change
- Darken the two light-colored text elements so they stand out clearly against their background.
The high-impact items are the ones quietly costing you customers who cannot get through the page, and they are usually quick to fix once you know where they are. Happy to walk your team through any of this.
When people ask ChatGPT, Claude, Perplexity, or Google's AI to recommend a business like yours, those tools read your site first. The less of your content they can read, the less likely they are to recommend you. Most of them - including OpenAI, Anthropic, and Perplexity - only read what your page shows right away and skip anything that loads a moment later; Google, Apple, and Microsoft's Bing are the main exceptions. This tab shows how much of your content AI can read today.
The site is in very good shape for AI readability - scoring 94 out of 100, with roughly 97% of content readable by most AI crawlers without JavaScript. The one change that benefits every page at once is fixing the heading order so the structure is easy for AI tools to follow.
This is a directional check (ShakaCode Agent Ready v1), like a speed score - use the findings below, not the number on its own.
How we score this
We score four things, weighted by how much they affect AI visibility: text that loads before JavaScript runs (40%, the biggest factor, because most AI tools do not run JavaScript), whether AI tools are allowed to read your site (25%), labels that tell AI what the page is about (20%), and a clear, logical layout (15%). Sites that send their content as ready-to-read HTML from the server score highest. For the main score we read your page the way a no-JavaScript AI crawler does - the raw page your server sends, before any browser code runs; a site that sends different HTML to specific AI bots may score differently. If we cannot read a page's server HTML, we say so instead of guessing a score, and a page that sends almost no content up front is capped low, since a crawler cannot see what is not there.
Can AI answer engines reach your site?
Search and AI answer engines mainly read and cite pages they are allowed to crawl. This is the same for every page on the site.
- robots.txt does not block the AI answer crawlers (the ones that cite sources).
- A sitemap is published, which gives crawlers a clearer page list to discover.
- No llms.txt (an optional, emerging guide for AI tools - low impact today).
- The pages we checked allow indexing.
About page
Reachable and well structured for AI assistants
97% of the content is in the server HTML, and the page is cleanly marked up.
Almost all of the About page text is available to AI assistants in the server HTML before JavaScript runs, putting it in good shape for being found - heading structure and missing image descriptions are the main gaps to close.
What to change
- Fix the heading order so levels do not skip - for example h2 then h3, not h2 then h4.
- Add a short description to each image that currently has none - 7 out of 9 are missing one.
See what we checked 3 groups
- 97% of the page's text is already in the page the server sends, before any JavaScript runs.
- The page title is in the page the server sends.
- The page description is in the page the server sends.
- Structured data is in the page the server sends, where AI crawlers can read it.
- The page the server sends already carries the main copy.
- Structured data found that helps machines understand the page (webpage, imageobject, breadcrumblist, website).
- The page has a title.
- The page has a meta description.
- Open Graph title, description, and image are all set.
- A canonical URL is declared.
- Page language is declared (en-US).
- The page has exactly one main heading.
- Heading levels skip around, so the outline is hard to follow.
- A <main> region marks the primary content.
- 94% of links have descriptive text.
- 2 of 9 images have alt text describing them.
- The page has 1364 words of text.
Apply page
Reachable and well structured for AI assistants
99% of the content is in the server HTML, and the page is cleanly marked up.
Nearly all of the Apply page content is readable by AI assistants before JavaScript runs, putting it in a strong position - heading structure, missing image descriptions, and a few vague links are the areas to improve.
What to change
- Fix the heading order so levels do not skip - for example h2 then h3, not h2 then h4.
- Add a short description to each image that currently lacks one - only 3 of 39 have one.
- Give descriptive text to any links that say 'click here' or show a bare URL.
See what we checked 3 groups
- 99% of the page's text is already in the page the server sends, before any JavaScript runs.
- The page title is in the page the server sends.
- The page description is in the page the server sends.
- Structured data is in the page the server sends, where AI crawlers can read it.
- The page the server sends already carries the main copy.
- Structured data found that helps machines understand the page (webpage, imageobject, breadcrumblist, website).
- The page has a title.
- The page has a meta description.
- Open Graph title, description, and image are all set.
- A canonical URL is declared.
- Page language is declared (en-US).
- The page has exactly one main heading.
- Heading levels skip around, so the outline is hard to follow.
- A <main> region marks the primary content.
- 90% of links have descriptive text.
- 3 of 39 images have alt text describing them.
- The page has 2653 words of text.
Events
Reachable and well structured for AI assistants
98% of the content is in the server HTML, and the page is cleanly marked up.
Almost all of the Events page content is visible to AI assistants in the server HTML, so the page reads well - the main things to address are the heading structure and descriptions for most of the page's images.
What to change
- Fix the heading order so levels do not skip - for example h2 then h3, not h2 then h4.
- Add a short description to each image that currently lacks one - only 3 of 24 have one.
See what we checked 3 groups
- 98% of the page's text is already in the page the server sends, before any JavaScript runs.
- The page title is in the page the server sends.
- The page description is in the page the server sends.
- Structured data is in the page the server sends, where AI crawlers can read it.
- The page the server sends already carries the main copy.
- Structured data found that helps machines understand the page (webpage, imageobject, breadcrumblist, website).
- The page has a title.
- The page has a meta description.
- Open Graph title, description, and image are all set.
- A canonical URL is declared.
- Page language is declared (en-US).
- The page has exactly one main heading.
- Heading levels skip around, so the outline is hard to follow.
- A <main> region marks the primary content.
- 94% of links have descriptive text.
- 3 of 24 images have alt text describing them.
- The page has 1865 words of text.
Homepage
Reachable and well structured for AI assistants
95% of the content is in the server HTML, and the page is cleanly marked up.
The homepage is nearly fully readable by AI assistants, with 95% of its content available before JavaScript runs - the only structural issue is how the headings are ordered, which affects how AI tools parse the page.
What to change
- Fix the heading order so levels do not skip - for example h2 then h3, not h2 then h4.
See what we checked 3 groups
- 95% of the page's text is already in the page the server sends, before any JavaScript runs.
- The page title is in the page the server sends.
- The page description is in the page the server sends.
- Structured data is in the page the server sends, where AI crawlers can read it.
- The page the server sends already carries the main copy.
- Structured data found that helps machines understand the page (webpage, imageobject, breadcrumblist, website).
- The page has a title.
- The page has a meta description.
- Open Graph title, description, and image are all set.
- A canonical URL is declared.
- Page language is declared (en-US).
- The page has exactly one main heading.
- Heading levels skip around, so the outline is hard to follow.
- A <main> region marks the primary content.
- 95% of links have descriptive text.
- 13 of 14 images have alt text describing them.
- The page has 817 words of text.
Scrolling the homepage
Reachable and well structured for AI assistants
95% of the content is in the server HTML, and the page is cleanly marked up.
Scrolling through the homepage shows the same strong picture - 95% of the content is in the HTML and readable by AI assistants, and heading order is the one structural issue to address.
What to change
- Fix the heading order so levels do not skip - for example h2 then h3, not h2 then h4.
See what we checked 3 groups
- 95% of the page's text is already in the page the server sends, before any JavaScript runs.
- The page title is in the page the server sends.
- The page description is in the page the server sends.
- Structured data is in the page the server sends, where AI crawlers can read it.
- The page the server sends already carries the main copy.
- Structured data found that helps machines understand the page (webpage, imageobject, breadcrumblist, website).
- The page has a title.
- The page has a meta description.
- Open Graph title, description, and image are all set.
- A canonical URL is declared.
- Page language is declared (en-US).
- The page has exactly one main heading.
- Heading levels skip around, so the outline is hard to follow.
- A <main> region marks the primary content.
- 95% of links have descriptive text.
- 13 of 14 images have alt text describing them.
- The page has 817 words of text.
The fix is making sure your full page content is there as soon as the page loads (server-rendering), and done well it usually speeds up the page for real visitors too. We do exactly this work every day at ShakaCode - reach out if it would help to talk through what we found.