bimm.com website review

• Google's speed test didn't respond

  Google's speed test didn't respond for this site, so speed and Core Web Vitals are not measured here. Your full playbook measures them.

Not measured in this review.

• Page weight: 5.6 MB

  5.6 MB

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

• 2 images over 500 KB

  2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

  Elements (2)

• 9 images below the first screen load straight away

  9 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• 5 images in older formats

  5 images (2.5 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.

  Elements (5)

• About 1.6 g of CO₂ per visit

  1.58 g

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

• 1 text element with low contrast

  1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  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)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• Zoom is disabled

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

  Elements (1)

• All page content should be contained by landmarks (1 element)

  All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 1 link without text

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

  Elements (1)

• Headings skip levels

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

  View sourceElements (1)

• 2 H1 headlines

  There are 2 <h1> headlines (“BIMM” and “We are a team of creative realists who combine te…”). One clear main headline is easier for people and search engines.

  View source

• 30 internal links, 4 external

  The homepage links to 30 pages on bimm.com and 4 external pages.

• Organization data is thin (3 of 6 facts)

  Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  View source

• No llms.txt

  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.

• 2 pages without a meta description

  /accessibility and /cookie-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (2)

• 2 pages with very little text

  /job-postings and /cookie-policy 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.

• 14 internal pages checked

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

• 3 small tap targets

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

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://pro.fontawesome.com/releases/v5.10.0/css/all.css' from origin 'https://bimm.com' h…”.

• No HSTS header

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

• No Content-Security-Policy

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

• HTTP/1.1 only

  The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

• No clickjacking protection

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

• No X-Content-Type-Options

  X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

• 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.

• No security.txt

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

• No CAA record

  bimm.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.

• DNSSEC is off

  bimm.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.

• No call to action on the first screen

  On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

• No social proof

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

• 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.

  View source

• No opening hours

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

• No form on the homepage

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

• 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 326 words of copy

  The homepage carries about 326 words of visible text.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be bimm.com is still delivered. Add a report address, check the reports, then move to quarantine.

• Email authentication score: 70/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.

• 1 tracker load before any consent

  1

  Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

• 1 cookie set on arrival

  1

  Opening the homepage sets 1 cookie (measured from a US location before any click).

• 9 other companies contacted

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