dirtygrinz.com website review

6 images could be 241 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, loox.io and Klaviyo and others), adding 1.5 MB and 1.1 s of main-thread time.

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

Shopify costs a phone 481 ms of main-thread work and 1.1 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.

loox.io costs a phone 423 ms of main-thread work and 17 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.

About 240 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

10 KiB could be saved by minifying JavaScript.

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.

2 KiB could be saved by minifying CSS.

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

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

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

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

The first text or image appears after 2.1 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 4.0 MB in 542 requests on a phone: scripts 1.5 MB (254), other files 1.3 MB (220) and images 868 KiB (42). Under 2 MB keeps phones on slow connections fast.

1 image (44 KiB) is 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 further down the page (84 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 1.14 g of CO₂e: 136.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

ARIA toggle fields must have an accessible name: 41 elements on the page fail this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

7 images have no alt text, which hurts accessibility and image search.

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

3 elements hidden from screen readers can still receive keyboard focus.

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

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

Your title is only 19 characters: “DirtyGrinz Clothing”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 112 pages on dirtygrinz.com and 3 external pages.

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.

Your homepage links to https://dirtygrinz.com/products/dg-i-am-ny-t-shirt, which answers with an error. Visitors hit a dead end and search engines drop it.

https://dirtygrinz.com/products/dg-i-am-ny-t-shirt-men-1 and https://dirtygrinz.com/products/dg-i-am-ny-men-2 all use the title “DG I AM NY T-Shirt | Heavyweight Streetwear Graphic Tee – DirtyGrinz”. Search engines can't tell which page to show for a search, so each competes with the others.

https://dirtygrinz.com/collections/new-arrivals, https://dirtygrinz.com/collections/men, https://dirtygrinz.com/collections/women, https://dirtygrinz.com/pages/about-dirtygrinz, https://dirtygrinz.com/collections/accessories and https://dirtygrinz.com/pages/dgdrops and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://dirtygrinz.com/products/dg-i-am-ny-t-shirt-men-1 and https://dirtygrinz.com/products/dg-i-am-ny-men-2 use the same meta description. A description written for each page earns more clicks.

https://dirtygrinz.com/collections/new-arrivals, https://dirtygrinz.com/collections/men, https://dirtygrinz.com/collections/women, https://dirtygrinz.com/pages/about-dirtygrinz, https://dirtygrinz.com/collections/accessories and https://dirtygrinz.com/pages/dgdrops and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Identifier 'section' has already been declared”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Meta Pixel and TikTok 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 14 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.