pixelplus.net website review

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

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

7 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 72 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 850 ms.

3 third-party services load with your homepage (Google Tag Manager, Pingdom RUM and Google Analytics), adding 292 KiB and 227 ms of main-thread time.

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

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

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

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

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

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

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

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 2.0 MB in 31 requests on a phone: images 1.5 MB (14), scripts 475 KiB (7) and fonts 41 KiB (4). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.9 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.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 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.

Your title is only 20 characters: “Anasayfa | Pixelplus”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 58 characters: “Ödüllü dijital pazarlama ve sosyal medya ajansı Pixelplus.”. 70 to 160 characters is enough to sell the click.

There are 5 <h1> headlines (“sürdürülebilir dijital pazarlama”, “yaratıcı dijital pazarlama çözümleri” and “her mecradan ilhamher içerikten keyif alıyoruz”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

There is no robots.txt at pixelplus.net/robots.txt, the first file search crawlers ask for.

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

The homepage links to 25 pages on pixelplus.net and 6 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 /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.

/sosyal-medya, /kvkk and /kariyer/hadi-tanisalim have no meta description, so Google writes the search snippet from whatever text it finds.

/calismalar/iyzico, /calismalar/turk-telekom-tivibu, /calismalar/sutas, /calismalar/opet-fuchs, /calismalar/garanti-bbva-pos and /calismalar/ziraat-katilim-web and 3 others use the same meta description. A description written for each page earns more clicks.

/kvkk has no <h1> headline, so visitors and search engines get no clear main topic.

/calismalar/zorlu-holding, /sosyal-medya, /odullerimiz, /markalarimiz and /kariyer/hadi-tanisalim 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 18 found) and read each the way a search engine does.

27 of 36 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”.

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

There is no form on the homepage, so every lead has to click through to another page first.

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 Analytics and Google Tag Manager (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 2 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.