safely6ft.com website review

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

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

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

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

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

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

Polyfills for old browsers add 9 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 third-party service load with your homepage (Google Fonts), adding 1 KiB and 0 ms of main-thread time.

Your largest element takes 27.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “unedited”.

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

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

The layout shifts by 0.268 while loading, so content jumps under the reader's thumb. Good is under 0.1.

49 images have no width and height attributes, so the layout jumps as each one loads.

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

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 8.2 MB in 88 requests on a phone: images 7.6 MB (30), scripts 369 KiB (23) and stylesheets 130 KiB (31). Under 2 MB keeps phones on slow connections fast.

imbranded-team-768x548.png weighs 776 KiB. On a phone connection a single image that size takes seconds.

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

2 images are downloaded at several times the size a phone draws them, for example jlr-white-no-bg-1.png at 4,152 px wide, shown at 50 px. Resized copies would save about 217 KiB.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 16 characters: “Home - iMBranded”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 51 pages on safely6ft.com and 103 external pages.

There is no /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.

/bmw has no meta description, so Google writes the search snippet from whatever text it finds.

/bmw took over 3 s to send its HTML from our server.

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

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

1 link go through two or more redirects, for example https://shop.imbranded.com/account.

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

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

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

imbranded.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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.

Social proof on the homepage: 58 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.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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

safely6ft.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

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