khachadoorian.com website review

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

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

4 third-party services load with your homepage (Squarespace, sqspcdn.com and Adobe TypeKit and others), adding 9.1 MB and 801 ms of main-thread time.

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

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

Squarespace costs a phone 676 ms of main-thread work and 921 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 135 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.

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

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

sqspcdn.com costs a phone 118 ms of main-thread work and 405 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.

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

1 image could be 40 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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.

Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OVERVIEW”.

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

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

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

Scripts block taps and scrolling for 385 ms 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 9.3 MB in 85 requests on a phone: images 7.7 MB (28), scripts 1.1 MB (40) and stylesheets 167 KiB (8). Under 2 MB keeps phones on slow connections fast.

Saucony_Mountain_High.gif weighs 1.3 MB. On a phone connection a single image that size takes seconds.

1 image (1.3 MB) 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.

1 image is downloaded at several times the size a phone draws it, for example Peroni-+-Giada_00220_G_w-logo.jpg at 1,231 px wide, shown at 392 px. Resized copies would save about 9 KiB.

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

Your title is 70 characters, so Google will cut it off around 60: “Commercial Photographer, Stills + Motion ⚡️Khachadoorian Studios 🎬🎙️”.

There are 13 <h1> headlines (“LATEST CAMPAIGNS”, “PORTRAIT” and “OVERVIEW”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 22 pages on khachadoorian.com and 8 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://khachadoorian.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://khachadoorian.com/portfolio/latest-campaigns, https://khachadoorian.com/portfolio/overview, https://khachadoorian.com/portfolio/medical, https://khachadoorian.com/portfolio/kids, https://khachadoorian.com/portfolio/roadtrip and https://khachadoorian.com/portfolio/video have no meta description, so Google writes the search snippet from whatever text it finds.

https://khachadoorian.com/about, https://khachadoorian.com/portfolio/latest-campaigns, https://khachadoorian.com/portfolio/portrait, https://khachadoorian.com/portfolio/overview, https://khachadoorian.com/portfolio/running and https://khachadoorian.com/portfolio/sports and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://khachadoorian.com/portfolio/latest-campaigns, https://khachadoorian.com/portfolio/fitness, https://khachadoorian.com/portfolio/medical, https://khachadoorian.com/portfolio/roadtrip and https://khachadoorian.com/portfolio/video 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 14 pages linked from your homepage and read each the way a search engine does.

2 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/63787365e0a27218f1a68de5/111/5c5…”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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