anlas.com website review

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

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

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

Reduce initial server response time. Google estimates savings of 906 ms on a phone.

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

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

About 658 KiB of JavaScript is downloaded but never used on this page.

7 third-party services load with your homepage (Google Tag Manager, Facebook and jQuery CDN and others), adding 1.0 MB and 517 ms of main-thread time.

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

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

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

Your server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

20 KiB could be saved by minifying CSS.

140 KiB could be saved by minifying JavaScript.

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

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

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.

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

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

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

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

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

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

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

Your homepage downloads 7.4 MB in 66 requests on a phone: images 5.5 MB (38), scripts 1.3 MB (13) and fonts 415 KiB (4). Under 2 MB keeps phones on slow connections fast.

4 images weigh 3.8 MB together. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example 1cffd395-1ed6-AN_DG_RMM_MUZE-02-01.png at 1,080 px wide, shown at 300 px. Resized copies would save about 2.3 MB.

16 images (5.0 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.

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

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

2 links inside paragraphs rely on colour alone to stand out.

All page content should be contained by landmarks: 3 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.

4 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.

Your title is only 29 characters: “ANLAS – Enhance your feelings”. 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 21 characters: “Enhance your feelings”. 70 to 160 characters is enough to sell the click.

There are 3 <h1> headlines (“Ortak Yol, Ortak Vizyon: Anlas Bayi Buluşması”, “Asfaltın Yeni Rotası: ANLAS CAPRA RD2” and “Honda Türkiye Heyeti Anlas Tesislerini Ziyaret Et…”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 84 pages on anlas.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.

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.

/, /tr and /en all use the title “ANLAS – Enhance your feelings”. Search engines can't tell which page to show for a search, so each competes with the others.

/tr/lastigini-bul, /tr/bayini-bul, /tr/capra-extreme, /tr/capra-r and /tr/capra-rd have no meta description, so Google writes the search snippet from whatever text it finds.

/tr and /en use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /tr/lastigini-bul, whose canonical is /tr/tr/lastigini-bul. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/tr/lastigini-bul has no <h1> headline, so visitors and search engines get no clear main topic.

/tr/bayini-bul, /tr/satis-servis-noktasi-ol, /tr, /en, /tr/capra-r and /tr/winter-grip-2-(sc-500) took over 3 s to send their HTML from our server.

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

15 of 66 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

Large scripts ship without source maps.

http://anlas.com does not redirect to https, so some visitors land on the insecure version.

1 link to other sites is dead, for example https://twitter.com/AnlasLastik (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 30 days; one year is the recommended minimum.

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

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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.

anlas.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.

anlas.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.

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.

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

anlas.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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