collegesnotes.com website review

About 526 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

8 third-party services load with your homepage (Firebase, Google/Doubleclick Ads and adeagle.app and others), adding 1.5 MB and 1.3 s of main-thread time.

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

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

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

11 images could be 680 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Firebase costs a phone 606 ms of main-thread work and 5 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.

Shopify costs a phone 70 ms of main-thread work and 864 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 31 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.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

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

25 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 18 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 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FurGone Advance Pet Hair Removal With FurGone Roller , you'…”.

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

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

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

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

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

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

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

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

Your homepage downloads 3.9 MB in 321 requests on a phone: scripts 1.5 MB (98), images 1.1 MB (37) and other files 973 KiB (148). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.

3 tap targets are too small or too close together to hit reliably with a finger.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Document should not have more than one banner landmark: 1 element on the page fails 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.

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

The homepage links to 30 pages on collegesnotes.com and 6 external pages.

https://collegesnotes.com/policies/privacy-policy, https://collegesnotes.com/policies/refund-policy, https://collegesnotes.com/policies/shipping-policy, https://collegesnotes.com/policies/terms-of-service and https://collegesnotes.com/policies/contact-information have no meta description, so Google writes the search snippet from whatever text it finds.

https://collegesnotes.com/policies/contact-information has 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.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Invalid regular expression: missing /”.

Chrome logged issues while loading the page (“Cookie”).

Requests the notification permission on page load.

Social proof on the homepage: 15 testimonial or review blocks. 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.

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

The homepage carries about 779 words of visible text.

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