Mobile speed report · June 24, 2026
How www.printivity.com loads on a phone
We loaded 6 of your pages on a typical phone over a normal cellular connection and recorded each one frame by frame - 82 frames in all. On a fast desktop these pages feel fine, which is exactly why what is below is easy to miss.
Captured June 24, 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 5.3s before the typical page here is usable, and 1 of your pages visibly jump around under their thumb while loading.
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.
Homepage
/Loads cleanly in 2.1s
▶ Press play - it loads cleanly. See for yourself.
Frame-by-frame breakdown 12 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.
The page loads in about 2 seconds and feels smooth when you click. One accessibility issue could make it harder for some people to use it.
Insights index
/insightsThe screen stays blank for 8.2s
Nothing at all is painted to the screen for that long - it can read as a broken page.
▶ Press play - the screen stays blank almost the entire time.
Frame-by-frame breakdown 10 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page loads extremely slowly - 8-10 seconds is way too long to wait. It downloads 2MB before showing the main content, and has 2 serious barriers for people using assistive technology.
Product: banners
/signage/bannersThe biggest piece of the page takes 7.4s to appear
Most of the page paints early, so the wait is easy to miss - but the biggest piece of the page only lands then.
▶ Press play - this is the 7.4s a phone visitor waits, in real time.
Frame-by-frame breakdown 17 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page loads too slowly - main content takes about 7 seconds to appear. It also has 2 major barriers for people using screen readers and other assistive tools.
Category: business cards
/business-cardsThe biggest piece of the page takes 6.7s to appear
Most of the page paints early, so the wait is easy to miss - but the biggest piece of the page only lands then.
▶ Press play - this is the 6.7s a phone visitor waits, in real time.
Frame-by-frame breakdown 14 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page starts loading but takes about 8 seconds before you can use it - everything feels frozen at first. It also has one accessibility issue.
Product: classic business cards
/business-cards/classic-business-cardsThe biggest piece of the page takes 4.8s to appear
Until then a visitor on a phone is looking at a mostly empty screen.
▶ Press play - this is the 4.8s a phone visitor waits, in real time.
Frame-by-frame breakdown 22 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page feels slow - main content appears after 5 seconds and uses too much JavaScript. It also has a couple accessibility issues for people using screen readers.
The rest of your pages, same pattern
- Products index /products The biggest piece of the page takes 2.6s to appear
Measured on June 24, 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.
Low-contrast text appears on every page and is the most consistent barrier for people with low vision. Two product pages also have invalid accessibility markup that can confuse assistive technology, and the products index has overlapping clickable elements that are hard to use by keyboard or touch - fixing those three pages first addresses the worst issues site-wide.
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.
Product: classic business cards
Four controls on this page use invalid accessibility markup that can confuse assistive technology, and a large amount of text is too light to read comfortably for people with low vision.
What to change
- Remove or correct the invalid accessibility attributes on the four controls that use them.
- Darken the light text so it is clearly readable against its background.
- Correct the heading structure so titles are ordered from large to small without gaps.
Product: banners
Five controls on this page use invalid accessibility markup that can confuse assistive technology, and much of the text is too light to read for people with low vision.
What to change
- Remove or correct the invalid accessibility attributes on the five controls that have them.
- Darken the light-colored text so it is easier to read against the background.
- Correct the heading order so section titles follow a logical large-to-small sequence.
Products index
Many clickable items on this page are nested inside other clickable items, and dozens of tap targets are too small or too close together, making the product grid hard to use for keyboard users and anyone on a touchscreen.
What to change
- Ensure no clickable element sits inside another clickable element across the product grid.
- Make the tap targets larger or space them further apart so they are easy to press on a phone.
- Darken the light text so it is easier to read.
Insights index
Three links on this page carry no readable text, so people navigating by keyboard or listening to the page cannot tell where those links go, and some text is also too faint for people with low vision to read.
What to change
- Add visible or descriptive text to the three links that currently have none so visitors can tell where they lead.
- Darken the light-colored text so it is easier to read.
- Ensure the page has one clearly defined main content area and that named section regions do not duplicate each other.
Category: business cards
Some text is too light for people with low vision to read easily, page titles skip levels in the heading order, and much of the content sits outside the regions that people navigating by keyboard rely on to jump between sections.
What to change
- Darken the light-colored text so it is clearly readable against its background.
- Wrap the remaining page sections in named content regions so keyboard users can navigate between them.
- Correct the heading order so page titles go from large to small without skipping levels.
Homepage
Some text on the homepage uses colors too faint for people with low vision to read comfortably, and a few page sections sit outside the navigation regions that keyboard users depend on to move around the page.
What to change
- Darken the light text so it stands out clearly against its background.
- Place all page sections inside properly named content regions so keyboard users can navigate between them.
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.
Most of your site's content is already readable by AI crawlers, and AI bots are allowed in with a sitemap in place. The single highest-impact fix across every page is adding social preview tags - currently missing on all pages - which helps AI assistants and social tools pull an accurate description when your site is mentioned.
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.
Product: classic business cards
Open Graph tags are incomplete (0/3 of title, description, image).
Add Open Graph title, description, and image tags for clean link previews.
About two-thirds of this product page's text is visible to most AI crawlers without JavaScript; the other third only loads after the browser runs the page, so some details may not reach AI assistants.
What to change
- Add social preview tags so AI tools and social platforms can show an accurate description when this page is shared.
- Fix the heading order so levels do not skip steps.
- Wrap the main content in a designated region so AI can identify which part is the primary content.
See what we checked 3 groups
- 64% 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 (faqpage, product).
- The page has a title.
- The page has a meta description.
- Open Graph tags are incomplete (0/3 of title, description, image).
- A canonical URL is declared.
- Page language is declared (en).
- The page has exactly one main heading.
- Heading levels skip around, so the outline is hard to follow.
- No <main> landmark, so agents must guess which part is the content.
- 80% of links have descriptive text.
- 9 of 9 images have alt text describing them.
- The page has 177 words of text (thin pages are hard for agents to summarize).
Product: banners
Open Graph tags are incomplete (0/3 of title, description, image).
Add Open Graph title, description, and image tags for clean link previews.
About two-thirds of this banner page's text is visible to most AI crawlers without JavaScript; the rest only loads after the browser runs the page, so some product details may not reach AI assistants.
What to change
- Add social preview tags so AI tools and social platforms can show an accurate description when this page is shared.
- Fix the heading order so levels do not skip steps.
- Wrap the main content in a designated region so AI can identify which part is the primary content.
See what we checked 3 groups
- 68% 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 (faqpage, product).
- The page has a title.
- The page has a meta description.
- Open Graph tags are incomplete (0/3 of title, description, image).
- A canonical URL is declared.
- Page language is declared (en).
- The page has exactly one main heading.
- Heading levels skip around, so the outline is hard to follow.
- No <main> landmark, so agents must guess which part is the content.
- 80% of links have descriptive text.
- 2 of 3 images have alt text describing them.
- The page has 158 words of text (thin pages are hard for agents to summarize).
Products index
No machine-readable structured data in the page the server sends.
Add schema.org structured data to the HTML the server sends.
All text on this page reaches most AI crawlers straight from the server with no JavaScript needed. The main gap is missing tags and markup that help AI understand and categorize what the page contains.
What to change
- Add structured data markup so AI and search tools know what type of content this page contains.
- Add social preview tags so AI tools and social platforms can show an accurate description when this page is shared.
- Fix the heading order so levels do not skip steps.
See what we checked 3 groups
- 100% 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.
- No machine-readable structured data in the page the server sends.
- The page the server sends already carries the main copy.
- No schema.org structured data, so machines must infer what the page is about.
- The page has a title.
- The page has a meta description.
- Open Graph tags are incomplete (0/3 of title, description, image).
- A canonical URL is declared.
- Page language is declared (en).
- 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.
- 97% of links have descriptive text.
- 48 of 48 images have alt text describing them.
- The page has 298 words of text.
Homepage
Reachable and well structured for AI assistants
100% of the content is in the server HTML, and the page is cleanly marked up.
All text on the homepage is visible to AI crawlers, but there are only 41 words - far too little for an AI assistant to summarize what the site does. Adding real body text is the top priority here.
What to change
- Add more descriptive body text so AI assistants have enough to understand and summarize what the site offers.
- Add social preview tags so AI tools and social platforms can show an accurate description when this page is shared.
- Give all links descriptive labels instead of generic text.
See what we checked 3 groups
- 100% 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 carries little to no body text.
- Structured data found that helps machines understand the page (organization).
- The page has a title.
- The page has a meta description.
- Open Graph tags are incomplete (0/3 of title, description, image).
- A canonical URL is declared.
- Page language is declared (en).
- The page has exactly one main heading.
- Headings follow a logical order.
- A <main> region marks the primary content.
- 80% of links have descriptive text.
- 10 of 10 images have alt text describing them.
- The page has 41 words of text (thin pages are hard for agents to summarize).
Category: business cards
Reachable and well structured for AI assistants
100% of the content is in the server HTML, and the page is cleanly marked up.
All text on this category page is visible to most AI crawlers without JavaScript. Small structural fixes to the heading order and page landmarks would help AI tools read and describe the content accurately.
What to change
- Add social preview tags so AI tools and social platforms can show an accurate description when this page is shared.
- Fix the heading order so levels do not skip steps.
- Wrap the main content in a designated region so AI can identify which part is the primary content.
See what we checked 3 groups
- 100% 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 (faqpage).
- The page has a title.
- The page has a meta description.
- Open Graph tags are incomplete (0/3 of title, description, image).
- A canonical URL is declared.
- Page language is declared (en).
- The page has exactly one main heading.
- Heading levels skip around, so the outline is hard to follow.
- No <main> landmark, so agents must guess which part is the content.
- 96% of links have descriptive text.
- 14 of 15 images have alt text describing them.
- The page has 421 words of text.
Insights index
Reachable and well structured for AI assistants
100% of the content is in the server HTML, and the page is cleanly marked up.
All content on this page reaches most AI crawlers without JavaScript. Minor fixes to heading structure and image descriptions would help AI tools read and summarize it more accurately.
What to change
- Fix the heading order so levels do not skip steps.
- Wrap the main content in a designated region so AI can identify which part is the primary content.
- Add descriptive alt text to the 3 images that currently have none.
See what we checked 3 groups
- 100% 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 (website, webpage, organization).
- 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.
- No <main> landmark, so agents must guess which part is the content.
- 91% of links have descriptive text.
- 16 of 19 images have alt text describing them.
- The page has 855 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.