2psstudios.com website review

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

Squarespace costs a phone 2.9 s of main-thread work and 3.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

8 third-party services load with your homepage (Squarespace, Google CDN and Stripe and others), adding 5.4 MB and 4.7 s of main-thread time.

Google CDN costs a phone 874 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.

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

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

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

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

Stripe costs a phone 293 ms of main-thread work and 286 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 Tag Manager costs a phone 255 ms of main-thread work and 188 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

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.

3 KiB could be saved by minifying CSS.

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

Your largest element takes 28.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Photography, Graphic Design, and Social Media Management Se…”.

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 7.5 MB in 152 requests on a phone: scripts 5.1 MB (87), images 1.0 MB (21) and other files 730 KiB (13). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (48 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 118 characters, so Google will cut it off around 60: “2Ps Studios - Photography, Graphic Design, and Social Media Management (Portraits, headsh…”.

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

Structured data found (LocalBusiness, Organization and WebSite) but with 3 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/61a58a71699860277d6…”.

The homepage links to 49 pages on 2psstudios.com and 0 external pages.

Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.2psstudios.com/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.

https://www.2psstudios.com/blog-for-seniors and https://www.2psstudios.com/blog-1 all use the title “BLOG FOR SENIOR PHOTOS — 2Ps Studios”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.2psstudios.com/blog-for-seniors and https://www.2psstudios.com/blog-1 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.2psstudios.com/blog-1, whose canonical is https://www.2psstudios.com/blog-for-seniors. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.2psstudios.com/graphic-design, https://www.2psstudios.com/headshots, https://www.2psstudios.com/weddings, https://www.2psstudios.com/contact and https://www.2psstudios.com/photography have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.2psstudios.com/contact has 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.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/61a58a71699860277d60f784/68/5c5a…”.

Chrome logged issues while loading the page (“Cookie”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 137 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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 7 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.