kidspartim.com website review

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

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

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

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

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

17 images could be 759 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

9 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.

About 311 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 440 ms faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, elfsightcdn.com and wdc.center and others), adding 415 KiB and 498 ms of main-thread time.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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.

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

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

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

Your largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Kargo slider yeni mobil”.

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

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

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

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

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

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

Your homepage downloads 3.0 MB in 68 requests on a phone: images 1.2 MB (40), scripts 789 KiB (11) and stylesheets 353 KiB (4). Under 2 MB keeps phones on slow connections fast.

15 images (1.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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

1 element has a tabindex above 0, which scrambles the keyboard order.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (9 elements).

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

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

No XML sitemap at https://www.kidspartim.com/sitemap.xml, so Google discovers your pages only by following links.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 429 pages on kidspartim.com and 11 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.

There is no https://www.kidspartim.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://www.kidspartim.com/sifremi-unuttum and https://www.kidspartim.com/lazer-sapka-modelleri all use the title “Parti Malzemeleri ve Doğum Günü Süslemeleri | KidsPartim”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kidspartim.com/sifremi-unuttum and https://www.kidspartim.com/lazer-sapka-modelleri use the same meta description. A description written for each page earns more clicks.

https://www.kidspartim.com/parti-sapkalari took over 3 s to send its HTML from our server.

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

2 images failed to load on a phone, for example https://s15.wdc.center/traffic.php?mkodu=2616&url=https%3A%2F%2Fwww.kidspartim.com%2F&t=Parti%20Malzemeleri%20ve%20Do%C4%9Fum%20G%C3%BCn%C3%BC%20S%C3%BCslemeleri%20|%20KidsPartim&ref=&agent=Mozilla/5..

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 error was logged to the browser console while the page loaded, for example “Unexpected token '<'”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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: 2 trust badges. 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 594 words of visible text.

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