aaprintsupplyco.com website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.

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

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

Your mobile performance score is 40 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.5 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 2.1 MB and 1.5 s of main-thread time.

8 images could be 326 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

About 124 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.

Facebook costs a phone 279 ms of main-thread work and 256 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.

Google CDN costs a phone 190 ms of main-thread work and 327 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.

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

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

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

129 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

Your largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Professional Equipment for Printing & Customization”.

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

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

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

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

Your homepage downloads 4.5 MB in 250 requests on a phone: scripts 2.7 MB (101), other files 872 KiB (107) and images 677 KiB (24). Under 2 MB keeps phones on slow connections fast.

1 image (170 KiB) is 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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

5 elements hidden from screen readers can still receive keyboard focus.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 321 pages on aaprintsupplyco.com and 21 external pages.

There is no /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.

We fetched 15 pages linked from your homepage (of 145 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=16018118&tm=gtm002&Ver=2&mid=9a31c84c-d6a3-46e0-b8ff-38b7cbb35ede&bo=1&sid=595e8970d22b11f18609b7cf04390325&vid=595eae50d22b11f18466b792decd879a&vids=1&msclkid=N&pi=91.

5 errors were logged to the browser console while the page loaded, for example “jQuery is not defined”.

1 link to other sites is dead, for example https://dtfstation.com/pages/prestige-a3-dtf-printers-live-training-sign-up (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

aaprintsupplyco.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

The homepage has only about 211 words of visible text; thin pages give Google and first-time buyers little to go on.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

DMARC is set to p=none, so mail pretending to be aaprintsupplyco.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 20 cookies (measured from a US location before any click).

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