papershoot.com website review

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

8 third-party services load with your homepage (Shopify, mediadelivery.net and Clarity and others), adding 2.7 MB and 1.3 s of main-thread time.

About 1.0 MB of JavaScript is downloaded but never used on this page.

Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

Shopify costs a phone 620 ms of main-thread work and 1.5 MB 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.

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

About 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

11 images could be 376 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

mediadelivery.net costs a phone 269 ms of main-thread work and 652 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.

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

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

133 KiB could be saved by minifying JavaScript.

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

66 KiB could be saved by minifying CSS.

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

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 page becomes fully interactive after 27.6 s. Good is under 3.8 s.

Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Load video:”.

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

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

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

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

Your homepage downloads 24.1 MB in 658 requests on a phone: media 17.9 MB (4), scripts 2.5 MB (217) and other files 1.7 MB (332). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example pro_d1b495af-b64a-48f2-810b-eeda9fc74e9a.gif at 400 px wide, shown at 100 px. Resized copies would save about 482 KiB.

2 images (553 KiB) 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.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

14 images have no alt text, which hurts accessibility and image search.

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

Headings skip levels (h1 → h3, h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is 85 characters, so Google will cut it off around 60: “Paper Shoot | Screen-Free Digital Camera with Film-Look Photos – Paper Shoot Official”.

1 link has no real href, so search engines can't follow it.

The homepage links to 126 pages on papershoot.com and 17 external pages.

Your homepage links to https://www.papershoot.com/collections/pro-add-ons-1, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.papershoot.com/pages/b2b-partnerships, https://www.papershoot.com/pages/contact-us, https://www.papershoot.com/policies/refund-policy, https://www.papershoot.com/policies/shipping-policy and https://www.papershoot.com/collections/function-card-1 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.papershoot.com/pages/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

The homepage carries about 703 words of visible text.

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

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

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.

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