Programmable

Website review, no card needed

luxera.com.tr logo

luxera.com.tr website review

Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 81 checks

This review found 44 issues worth fixing on luxera.com.tr, 19 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

57F

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.6 s2.3 sMay 2Oct 173.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.6 s
Jun 20, 20262.5 s
Jun 27, 20262.6 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20263.0 s
Sep 19, 20263.2 s
Sep 26, 20263.3 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
396 ms207 msMay 2Oct 17368 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026229 ms
May 9, 2026237 ms
May 16, 2026240 ms
May 23, 2026240 ms
May 30, 2026238 ms
Jun 6, 2026247 ms
Jun 13, 2026251 ms
Jun 20, 2026237 ms
Jun 27, 2026237 ms
Jul 4, 2026238 ms
Jul 11, 2026242 ms
Jul 18, 2026298 ms
Jul 25, 2026310 ms
Aug 1, 2026315 ms
Aug 8, 2026327 ms
Aug 15, 2026295 ms
Aug 22, 2026281 ms
Aug 29, 2026277 ms
Sep 5, 2026286 ms
Sep 12, 2026302 ms
Sep 19, 2026330 ms
Sep 26, 2026341 ms
Oct 3, 2026361 ms
Oct 10, 2026374 ms
Oct 17, 2026368 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

luxera.com.tr (opens in a new tab)
Full-page screenshot of luxera.com.tr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. luxera.com.tr at 1.1 s1.1 s
  2. luxera.com.tr at 2.2 s2.2 s
  3. luxera.com.tr at 3.2 s3.2 s
  4. luxera.com.tr at 4.3 s4.3 s
  5. luxera.com.tr at 5.4 s5.4 s
  6. luxera.com.tr at 6.5 s6.5 s
  7. luxera.com.tr at 7.6 s7.6 s
  8. luxera.com.tr at 8.7 s8.7 s

Speed

11 to fix40

  • Reduce unused JavaScript

    1.6 s · 793 KiB

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

  • Mobile performance score: 40

    40/100

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

  • Main-thread work: 5.8 s

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

  • Use efficient cache lifetimes

    150 ms · 3.6 MB

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

  • Improve image delivery

    2.1 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.1 MB and 1.4 s of main-thread time.

  • Google Tag Manager adds 744 ms

    744 ms

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

  • Legacy JavaScript

    350 ms · 34 KiB

    Polyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • 19 long tasks on the main thread

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

  • Facebook adds 293 ms

    293 ms

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

  • 2,125 HTML elements

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

  • Render-blocking requests

    150 ms

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

  • Reduce unused CSS

    24 KiB

    About 24 KiB of CSS is downloaded but never applied on this page.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed

  • Server response: 384 ms

    384 ms

    Your server sent the HTML in 384 ms, well inside Google's 600 ms guideline.

Core Web Vitals

14 to fix0

  • Fails Core Web Vitals for real visitors

    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-user LCP: 4.4 s

    4.4 s

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

  • Real-user CLS: 0.39

    0.39

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 11.9 s

    11.9 s

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

  • Speed Index: 19.9 s

    19.9 s

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

  • Time to Interactive: 31.7 s

    31.7 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user INP: 298 ms

    298 ms

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

  • Tap response (INP) got 59% slower for real visitors

    +59%

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

  • Largest content (LCP) got 42% slower for real visitors

    +42%

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 1 image without width and height

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

1 checks passed

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix64

  • Page weight: 8.1 MB in 133 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 133 requests on a phone: images 4.5 MB (28), scripts 2.7 MB (62) and HTML 795 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    image is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (100 KiB) is 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.

  • About 2.3 g of CO₂ per visit

    2.29 g

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

1 checks passed

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 10098

  • 9 form fields without a label

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

2 checks passed

  • Every image has alt text

    All 132 images in the HTML carry an alt attribute.

  • 19 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 19 WCAG 2.2 A/AA and best-practice rules on the phone render: 19 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9169

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • No canonical URL

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 59 internal links, 26 external

    The homepage links to 59 pages on luxera.com.tr and 26 external pages.

3 checks passed

  • Title: 50 characters

    Your title is a healthy 50 characters: “Luxera GYO | Yatırımda Gücün Yaşamda Lüksün Adresi”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://luxera.com.tr/sitemap.xml.

AI search readiness

1 to fix88

  • No Organization structured data

    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.

  • No llms.txt

    There is no https://luxera.com.tr/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.

2 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,881 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix75

  • 8 pages without a title

    https://luxera.com.tr/kurumsal/hakkimizda, https://luxera.com.tr/sulkent, https://luxera.com.tr/nevbahar-suites, https://luxera.com.tr/projeler/devam-eden-projeler, https://luxera.com.tr/luxera-topkapi and https://luxera.com.tr/nevbahar-life and 2 others have no <title>, so Google invents the link text in results.

  • 9 pages without a meta description

    https://luxera.com.tr/kurumsal/hakkimizda, https://luxera.com.tr/yatirimci-iliskileri, https://luxera.com.tr/sulkent, https://luxera.com.tr/nevbahar-suites, https://luxera.com.tr/projeler/devam-eden-projeler and https://luxera.com.tr/luxera-topkapi and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://luxera.com.tr/kampanyalar, https://luxera.com.tr/kurumsal/hakkimizda, https://luxera.com.tr/yatirimci-iliskileri, https://luxera.com.tr/iletisim, https://luxera.com.tr/rehber and https://luxera.com.tr/kurumsal/guven-ve-sorumluluk-yaklasimimiz/isg-ve-cevre-politikamiz and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://luxera.com.tr/kampanyalar, https://luxera.com.tr/kurumsal/hakkimizda, https://luxera.com.tr/yatirimci-iliskileri and https://luxera.com.tr/iletisim took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9684

  • 2 broken images

    2 images failed to load on a phone, for example https://luxera.com.tr/_next/image?url=https%3A%2F%2Fcdn.luxera.com.tr%2Fuploads%2Fslider%2Fsulkent-ekim-banner-web-1920x960-1_2026-10-15_07-37-56_5dac0e.jpg&w=640&q=90.

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    22 of 24 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50

  • No call to action on the first screen

    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 calls to action

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

  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • A 8-field form

    Your longest form asks for 8 fields (4 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No risk reducer

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

  • About 1,448 words of copy

    The homepage carries about 1,448 words of visible text.

3 checks passed

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight 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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 27 other companies contacted

    Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at luxera.com.tr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on luxera.com.tr, including 25 speed issues, 5 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25