smallcase.com website review

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

About 1.5 MB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 799 KiB and 470 ms of main-thread time.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

Real visitors wait 434 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Phone Mockup”.

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 202 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.4 MB in 249 requests on a phone: scripts 2.5 MB (94), other files 992 KiB (62) and images 698 KiB (55). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example generic_smallcase.45949657.png at 384 px wide, shown at 100 px. Resized copies would save about 32 KiB.

1 image (81 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.25 g of CO₂e: 149.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

The homepage links to 29 pages on smallcase.com and 17 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.smallcase.com/explore/smallcases, https://www.smallcase.com/explore/mutual-funds and https://www.smallcase.com/explore/stocks have no <title>, so Google invents the link text in results.

https://www.smallcase.com/explore/smallcases, https://www.smallcase.com/explore/mutual-funds and https://www.smallcase.com/explore/stocks have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.smallcase.com/collection/etf-picks-694a653d227b8fd5bfe8cecc, whose canonical is https://www.smallcase.com/collection/etf-portfolios-694a653d227b8fd5bfe8cecc. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.smallcase.com/explore/smallcases, https://www.smallcase.com/explore/mutual-funds, https://www.smallcase.com/explore/stocks and https://www.smallcase.com/blog have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.smallcase.com/explore/smallcases, https://www.smallcase.com/explore/mutual-funds and https://www.smallcase.com/explore/stocks have 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 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

Large scripts ship without source maps.

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

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

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