evidea.com website review

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

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

Sentry costs a phone 1.3 s of main-thread work and 31 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Sentry, Google Tag Manager and mindbehind.com and others), adding 5.4 MB and 4.6 s of main-thread time.

56 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

Insider costs a phone 587 ms of main-thread work and 1.7 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.

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

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

mindbehind.com costs a phone 596 ms of main-thread work and 1.2 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.

akinoncloud.com costs a phone 527 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.

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

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

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.

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

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

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

Real visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Kasım İndirim Festivali Başladı”.

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

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

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

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

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

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

The layout shifts by 0.154 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' largest content (lcp) went from 2.1 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.0 MB in 495 requests on a phone: images 7.2 MB (328), scripts 4.0 MB (41) and fonts 395 KiB (5). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example a5c96884-5907-40fb-b346-3b57b6c23d1d.png at 3,200 px wide, shown at 360 px. Resized copies would save about 1.1 MB.

6 images further down the page (1.2 MB) 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 3.41 g of CO₂e: 409.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

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

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

7 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. (37 elements).

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Your title is only 24 characters: “Burada her şey evim için”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Structured data found ((untyped) and Organization) but with 8 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

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

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

The homepage links to 739 pages on evidea.com and 8 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.

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

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

1 image failed to load on a phone, for example https://www.evidea.com/.

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

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

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

evidea.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

evidea.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

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 1,077 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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