searchlightcontent.com website review

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

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

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

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

7 third-party services load with your homepage (Squarespace, Google Tag Manager and Adobe TypeKit and others), adding 5.2 MB and 604 ms of main-thread time.

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

Squarespace costs a phone 419 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.

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

Google Tag Manager costs a phone 170 ms of main-thread work and 311 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.

8 long tasks block the main thread while loading, the longest for 180 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).

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

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

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.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Reasons to get in touch: You know what to say. You just don…”.

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

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

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

Scripts block taps and scrolling for 223 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 5.2 MB in 88 requests on a phone: images 3.5 MB (25), scripts 1.3 MB (30) and fonts 328 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example Ashley_Cummings_Logo_reversed+type.png at 1,500 px wide, shown at 96 px. Resized copies would save about 80 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 1.48 g of CO₂e: 177.2 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.

3 links inside paragraphs rely on colour alone to stand out.

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

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

There are 7 <h1> headlines (“”, “Wrap your target audience around your finger with…” and “Hire an experienced freelance SaaS writer (me).”). One clear main headline is easier for people and search engines.

Your meta description is 221 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/5cf9472701bfbd0001a…”.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 38 pages on searchlightcontent.com and 5 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.ashleyrcummings.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.ashleyrcummings.com/newsletter, https://www.ashleyrcummings.com/products-1 and https://www.ashleyrcummings.com/hire-me 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 9 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/sitecss/5cf9472701bfbd0001abc22b/203/52a74dafe4b073…”.

Social proof on the homepage: 1 testimonial or review block. 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.

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 1,129 words of visible text.

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