kandrphotography.net website review

12 images could be 33.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 203.0 s faster on a phone.

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

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

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

About 53 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

3 third-party services load with your homepage (Facebook, Pinterest and Google Fonts), adding 158 KiB and 49 ms of main-thread time.

1 long task block the main thread while loading, the longest for 59 ms. During a long task the page ignores taps.

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

About 50 KiB of CSS is downloaded but never applied on this page.

11 KiB could be saved by minifying JavaScript.

9 KiB could be saved by minifying CSS.

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 177.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

2 images 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.

11 images weigh 33.7 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 34.2 MB in 36 requests on a phone: images 33.8 MB (15), scripts 188 KiB (11) and fonts 152 KiB (4). Under 2 MB keeps phones on slow connections fast.

11 images are downloaded at several times the size a phone draws them, for example 1100.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 25.9 MB.

12 images (33.8 MB) 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 9.70 g of CO₂e: 1164.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Your title is only 21 characters: “K&amp;R Photography -”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.kandrphotography.net/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at kandrphotography.net/robots.txt, the first file search crawlers ask for.

5 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 12 pages on kandrphotography.net and 6 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.kandrphotography.net/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.kandrphotography.net/home, https://www.kandrphotography.net/about-us, https://www.kandrphotography.net/galleries, https://www.kandrphotography.net/info and https://www.kandrphotography.net/blog and 1 other all use the title “K&amp;R Photography -”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kandrphotography.net/home, https://www.kandrphotography.net/about-us, https://www.kandrphotography.net/galleries, https://www.kandrphotography.net/info, https://www.kandrphotography.net/blog and https://www.kandrphotography.net/contact use the same meta description. A description written for each page earns more clicks.

https://www.kandrphotography.net/home, https://www.kandrphotography.net/about-us, https://www.kandrphotography.net/galleries, https://www.kandrphotography.net/info, https://www.kandrphotography.net/blog and https://www.kandrphotography.net/contact 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.

https://www.kandrphotography.net/home, https://www.kandrphotography.net/about-us, https://www.kandrphotography.net/galleries and https://www.kandrphotography.net/info took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://www.kandrphotography.net/v1site_images/backgrounds/.

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

Social proof on the homepage: 24 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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 180 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads 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 1 cookie (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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.