matjarpanda.com website review

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

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

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

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

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

8 third-party services load with your homepage (zid.store, Google Tag Manager and Facebook and others), adding 9.1 MB and 1.8 s of main-thread time.

zid.store costs a phone 553 ms of main-thread work and 8.0 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 471 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.

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

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

Facebook costs a phone 305 ms of main-thread work and 267 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.

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

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

129 KiB could be saved by minifying JavaScript.

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

20 KiB could be saved by minifying CSS.

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.

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.

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

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

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

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

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

Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.

Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.1 MB in 329 requests on a phone: images 6.8 MB (110), scripts 1.8 MB (155) and fonts 370 KiB (6). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1,003 KiB together. On a phone connection a single image that size takes seconds.

13 images are downloaded at several times the size a phone draws them, for example 524a4d79-f1e6-47ce-bd8a-2046159440bd.jpg at 770 px wide, shown at 106 px. Resized copies would save about 620 KiB.

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

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

3 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

All page content should be contained by landmarks: 2 elements on the page fail 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

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

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

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

The homepage links to 446 pages on matjarpanda.com and 10 external pages.

There is no https://matjarpanda.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://matjarpanda.com/categories/1384346/cat-supplies, https://matjarpanda.com/categories/1441049/%D8%A7%D9%84%D9%82%D8%B7%D8%B7-%D8%A7%D9%84%D8%B5%D8%BA%D9%8A%D8%B1%D8%A9, https://matjarpanda.com/categories/1387611/cats-food-kitten-food, https://matjarpanda.com/categories/1386679/cat-supplies-cats-food, https://matjarpanda.com/categories/1387670/cats-food-dry-food and https://matjarpanda.com/categories/1387669/cat-wet-food and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://matjarpanda.com/categories/1384346/cat-supplies, https://matjarpanda.com/categories/1441049/%D8%A7%D9%84%D9%82%D8%B7%D8%B7-%D8%A7%D9%84%D8%B5%D8%BA%D9%8A%D8%B1%D8%A9, https://matjarpanda.com/categories/1387611/cats-food-kitten-food, https://matjarpanda.com/categories/1386679/cat-supplies-cats-food, https://matjarpanda.com/categories/1387670/cats-food-dry-food and https://matjarpanda.com/categories/1387669/cat-wet-food and 9 others 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.

https://matjarpanda.com/categories/1386679/cat-supplies-cats-food, https://matjarpanda.com/categories/1387576/cat-health-spayed-and-neutered-cases, https://matjarpanda.com/categories/1387619/cats-food-food-for-digestive-sensitivities, https://matjarpanda.com/categories/1387618/cats-food-food-for-weight-control, https://matjarpanda.com/categories/1387610/cats-food-adult-cat-food and https://matjarpanda.com/categories/1401912/senior-cats-food and 1 other took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 196 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.

6 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 ()”.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 71 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 194 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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