dopeboo.com website review

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

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

The page has 5,491 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

18 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Cloudinary costs a phone 0 ms of main-thread work and 627 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.

3 long tasks block the main thread while loading, the longest for 149 ms. During a long task the page ignores taps.

3 third-party services load with your homepage (Google Fonts, Gravatar and Cloudinary), adding 666 KiB and 2 ms of main-thread time.

1 file is served with short cache lifetimes, so returning visitors download them again (5 KiB).

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 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

3 images 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 2.6 MB in 165 requests on a phone: images 2.2 MB (23), scripts 205 KiB (61) and stylesheets 90 KiB (77). Under 2 MB keeps phones on slow connections fast.

11 images (1.3 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.

1 image is downloaded at several times the size a phone draws it, for example EX_AMANITA_GUMMIES_1-1_1c3ac5bc-97cb-472c-b43f-215abb7d552e_ at 940 px wide, shown at 150 px. Resized copies would save about 325 KiB.

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

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

1 link inside paragraphs relies on colour alone to stand out.

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

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.

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

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

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

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 976 pages on dopeboo.com and 44 external pages.

Your Organization JSON-LD is missing url, logo, 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.

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.

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

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

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

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

4 links go through two or more redirects, for example https://www.facebook.com/sharer/sharer.php?u=https://dopeboo.com/blogs/guide/what-flavor-layers-make-thc-seltzers-and-spirits-more-enjoyable-to-sip/.

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

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

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

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

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.

Social proof on the homepage: 6 trust badges. 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 link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 2,146 words of visible text.

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

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.

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