bensly.com website review

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

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 900 ms.

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

8 third-party services load with your homepage (Shopify, Facebook and Google Analytics and others), adding 658 KiB and 405 ms of main-thread time.

About 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 6.3 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 6.6 s. Good is under 3.8 s.

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

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.

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

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

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

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

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

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

Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.

No XML sitemap at https://bensly.com/sitemap.xml, so Google discovers your pages only by following links.

Your <h1> is empty.

The homepage links to 23 pages on bensly.com and 4 external pages.

There is no https://bensly.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://bensly.com/a/review/all and https://bensly.com/collections/all-bensly-products have no meta description, so Google writes the search snippet from whatever text it finds.

https://bensly.com/products/mens-tshirt-ultrasoft-tencel-tee and https://bensly.com/products/mens-tshirt-ultrasoft-tencel-fitted-tee use the same meta description. A description written for each page earns more clicks.

https://bensly.com/collections/underwear, https://bensly.com/collections/t-shirts-1, https://bensly.com/collections/pima-series and https://bensly.com/collections/all-bensly-products have no <h1> headline, so visitors and search engines get no clear main topic.

https://bensly.com/a/review/all, https://bensly.com/collections/underwear, https://bensly.com/collections/t-shirts-1, https://bensly.com/collections/pima-series and https://bensly.com/collections/all-bensly-products 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://bensly.com/a/review/all took over 3 s to send its HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

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