someonesomewhere.com website review

77 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).

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

Your mobile performance score is 62 (desktop: 84). Pages that score under 90 lose visitors before the first paint.

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

5 images could be 466 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

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

4 third-party services load with your homepage (Google Tag Manager, Google Fonts and FontAwesome CDN and others), adding 253 KiB and 192 ms of main-thread time.

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

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

3 KiB could be saved by minifying CSS.

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

Your largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (7.6 s).

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

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

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

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 2.6 MB in 85 requests on a phone: images 2.0 MB (15), scripts 438 KiB (30) and stylesheets 130 KiB (32). Under 2 MB keeps phones on slow connections fast.

4 images (507 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.

1 image is downloaded at several times the size a phone draws it, for example someone-somewhere_video_homepage.jpg at 1,744 px wide, shown at 360 px. Resized copies would save about 136 KiB.

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 38 pages on someonesomewhere.com and 7 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://someonesomewhere.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://someonesomewhere.com/solutions/reverse-engineering, https://someonesomewhere.com/solutions/new-product-development, https://someonesomewhere.com/solutions/catalog-sourcing, https://someonesomewhere.com/solutions/circuloom, https://someonesomewhere.com/capabilities/artisans and https://someonesomewhere.com/capabilities/manufacturing and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://someonesomewhere.com/solutions/reverse-engineering, https://someonesomewhere.com/solutions/new-product-development, https://someonesomewhere.com/solutions/catalog-sourcing, https://someonesomewhere.com/solutions/circuloom, https://someonesomewhere.com/capabilities/artisans and https://someonesomewhere.com/capabilities/manufacturing and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://someonesomewhere.com/solutions/reverse-engineering, https://someonesomewhere.com/solutions/new-product-development, https://someonesomewhere.com/solutions/catalog-sourcing, https://someonesomewhere.com/solutions/circuloom, https://someonesomewhere.com/capabilities/artisans and https://someonesomewhere.com/capabilities/manufacturing and 3 others took over 3 s to send their HTML from our server.

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

3 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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 57 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 Google Ads, Google Analytics and Google Tag Manager (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 9 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.