2kool4skool.com website review

76 files are served with short cache lifetimes, so returning visitors download them again (3.5 MB).

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Bigcommerce and others), adding 4.5 MB and 1.5 s of main-thread time.

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

Bigcommerce costs a phone 280 ms of main-thread work and 3.9 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 60 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.

Google Tag Manager costs a phone 488 ms of main-thread work and 178 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.

Google CDN costs a phone 408 ms of main-thread work and 40 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.

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

33 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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

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

Your largest element takes 20.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Professional Ukuleles”.

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

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

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

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

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

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

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.6 MB in 134 requests on a phone: images 3.5 MB (47), scripts 675 KiB (44) and fonts 176 KiB (5). Under 2 MB keeps phones on slow connections fast.

4 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example mim-6-string-uke-1-edit__32797.jpg at 1,880 px wide, shown at 390 px. Resized copies would save about 1.9 MB.

10 images (3.1 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.

5 images further down the page (403 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.30 g of CO₂e: 155.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 1,625 pages on 2kool4skool.com and 12 external pages.

/guitar-bass/guitars/acoustic-guitars/12-string and /guitar-bass/guitars/electric-guitars/12-string-guitars have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://cdn10.bigcommerce.com/s-j897kmotiv/product_images/uploaded_images/img-email.jpg.

8 of 37 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 “Failed to load resource: net::ERR_FAILED”.

2 images are served at too low a resolution for sharp phone screens.

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.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

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

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

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

2kool4skool.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.

2kool4skool.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.

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

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

DMARC is set to p=none, so mail pretending to be 2kool4skool.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.

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