dopeslimes.com website review

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

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

Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 6.9 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Shopify, Judge.me and useamp.com and others), adding 11.3 MB and 1.4 s of main-thread time.

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

Shopify costs a phone 815 ms of main-thread work and 2.6 MB 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.

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

qikify.com costs a phone 51 ms of main-thread work and 7.5 MB 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.

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

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

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

cornercart.io costs a phone 43 ms of main-thread work and 527 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.

6 KiB could be saved by minifying JavaScript.

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

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

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

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

Scripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.

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

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

Your homepage downloads 15.3 MB in 292 requests on a phone: images 11.5 MB (52), scripts 2.0 MB (91) and other files 1.3 MB (113). Under 2 MB keeps phones on slow connections fast.

5 images weigh 6.8 MB together. On a phone connection a single image that size takes seconds.

13 images (7.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.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://dopeslimes.com/search?q={search_term_string}")”.

3 links have no real href, so search engines can't follow them.

The homepage links to 127 pages on dopeslimes.com and 10 external pages.

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

9 of 20 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 “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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