beeslighting.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user INP: 204 ms

  204 ms

  Real visitors wait 204 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

• Tap response (INP) held steady for real visitors

  -2%

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

• Page weight: 3.3 MB

  3.3 MB

  Your homepage downloads 3.3 MB on a phone, 223 KiB of it images (7%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  banner-home-fall-warmup-sale-mobile.webp 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).

  Elements (1)

• About 0.9 g of CO₂ per visit

  0.93 g

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

• 10 text elements with low contrast

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

  Elements (3)

• 2 tap targets too small

  2 tap targets are too small or too close together to hit reliably with a finger.

  Elements (2)

• Frames without titles

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

  Elements (1)

• Scrollable region must have keyboard access (1 element)

  Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• All page content should be contained by landmarks (12 elements)

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

  Elements (3)

• 17 links without text

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

• Alternative text of images should not be repeated as text (15 elements)

  Alternative text of images should not be repeated as text: 15 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Headings should not be empty (9 elements)

  Headings should not be empty: 9 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Headings skip levels

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

  View sourceElements (1)

• One H1 headline

  Your <h1> is empty.

  View source

• 683 internal links, 15 external

  The homepage links to 683 pages on beeslighting.com and 15 external pages.

• 15 internal pages checked

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

• 3 JavaScript errors while loading

  3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'dataset')”.

• Short HSTS lifetime

  HSTS is set, but max-age is 91 days; one year is the recommended minimum.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• DNSSEC is off

  beeslighting.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• Local business without LocalBusiness data

  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.

• No analytics detected

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

• No opening hours

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

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• No risk reducer

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

• About 1,281 words of copy

  The homepage carries about 1,281 words of visible text.

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

• Email authentication score: 90/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 7 trackers load before any consent

  7

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (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.

• 20 cookies set on arrival

  20

  Opening the homepage sets 20 cookies (measured from a US location before any click).

• No consent tool detected

  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.

• 40 other companies contacted

  Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.