crystalbarbeephotography.com website review

About 890 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.2 s faster on a phone.

7 third-party services load with your homepage (Squarespace, Google CDN and Other Google APIs/SDKs and others), adding 3.1 MB and 768 ms of main-thread time.

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

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

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

Squarespace costs a phone 449 ms of main-thread work and 1.0 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.

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

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

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.1 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

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

Your largest element takes 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Crystal Barbee Photography”.

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

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

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 3.6 MB in 101 requests on a phone: scripts 1.7 MB (34), images 1.0 MB (37) and other files 518 KiB (7). Under 2 MB keeps phones on slow connections fast.

crystal_name+gray.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

10 images further down the page (248 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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 should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 67 characters, so Google will cut it off around 60: “Buford Newborn and Family Photographer | Crystal Barbee Photography”.

There are 2 <h1> headlines (“"THE BEAUTY OF A WOMAN MUST BE SEEN FROM IN HER E…” and “Let's Work Together!”). One clear main headline is easier for people and search engines.

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5a3add118dd041ae441…”.

The homepage links to 26 pages on crystalbarbeephotography.com and 31 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.crystalbarbeephotography.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.crystalbarbeephotography.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.crystalbarbeephotography.com/home all use the title “Buford Newborn and Family Photographer | Crystal Barbee Photography”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.crystalbarbeephotography.com/galleries, https://www.crystalbarbeephotography.com/about, https://www.crystalbarbeephotography.com/details, https://www.crystalbarbeephotography.com/contact, https://www.crystalbarbeephotography.com/about-index and https://www.crystalbarbeephotography.com/cbp-blog have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.crystalbarbeephotography.com/galleries, https://www.crystalbarbeephotography.com/contact and https://www.crystalbarbeephotography.com/cbp-blog have 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 7 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://images.squarespace-cdn.com/content/v1/5a3add118dd041ae441d6e53/1513812570064-0HGNTR8XGXH4KU7ZE346/Line2.png?format=100w.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

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.

The homepage carries about 313 words of visible text.

Opening the homepage sets 3 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.