Website review, no card needed

dreametech.com.tr logo

dreametech.com.tr website review

Visit site (opens in a new tab)Reviewed 4 November 202641 issues · 89 checks

This review found 41 issues worth fixing on dreametech.com.tr, 17 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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

Real-visitor load time (LCP)75th percentile, phones
2.9 s1.9 sMay 16Oct 312.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.8 s
Jun 6, 20262.7 s
Jun 13, 20262.5 s
Jun 20, 20262.2 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.2 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
231 ms163 msMay 16Oct 31200 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026223 ms
May 23, 2026217 ms
May 30, 2026212 ms
Jun 6, 2026209 ms
Jun 13, 2026204 ms
Jun 20, 2026201 ms
Jun 27, 2026200 ms
Jul 4, 2026198 ms
Jul 11, 2026195 ms
Jul 18, 2026185 ms
Jul 25, 2026179 ms
Aug 1, 2026173 ms
Aug 8, 2026171 ms
Aug 15, 2026172 ms
Aug 22, 2026173 ms
Aug 29, 2026174 ms
Sep 5, 2026175 ms
Sep 12, 2026176 ms
Sep 19, 2026182 ms
Sep 26, 2026189 ms
Oct 3, 2026194 ms
Oct 10, 2026198 ms
Oct 17, 2026201 ms
Oct 24, 2026201 ms
Oct 31, 2026200 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

Full-page screenshot of dreametech.com.tr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dreametech.com.tr at 1.1 s1.1 s
  2. dreametech.com.tr at 2.2 s2.2 s
  3. dreametech.com.tr at 3.3 s3.3 s
  4. dreametech.com.tr at 4.4 s4.4 s
  5. dreametech.com.tr at 5.5 s5.5 s
  6. dreametech.com.tr at 6.6 s6.6 s
  7. dreametech.com.tr at 7.7 s7.7 s
  8. dreametech.com.tr at 8.8 s8.8 s

Speed

14 to fix39
  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 6.4 s

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

  • 4,945 HTML elements

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

  • 8 third-party services on the page

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

  • Reduce unused JavaScript

    750 ms · 754 KiB

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

  • Google Tag Manager adds 997 ms

    997 ms

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

  • Shopify adds 128 ms

    128 ms

    Shopify costs a phone 128 ms of main-thread work and 7.5 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.

  • Reduce unused CSS

    750 ms · 117 KiB

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

  • Minify JavaScript

    450 ms · 53 KiB

    53 KiB could be saved by minifying JavaScript.

  • ZenDesk adds 364 ms

    364 ms

    ZenDesk costs a phone 364 ms of main-thread work and 431 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.

  • Facebook adds 306 ms

    306 ms

    Facebook costs a phone 306 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.

  • 16 long tasks on the main thread

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

  • Use efficient cache lifetimes

    292 KiB

    13 files are served with short cache lifetimes, so returning visitors download them again (292 KiB).

  • Minify CSS

    150 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • Improve image delivery

    82 KiB

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

  • 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: 15 ms

    15 ms

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

Core Web Vitals

8 to fix33
  • 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.

  • Largest Contentful Paint: 43.6 s

    43.6 s

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

  • Speed Index: 16.7 s

    16.7 s

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

  • Time to Interactive: 43.7 s

    43.7 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user INP: 205 ms

    205 ms

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

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

6 checks passed
  • Real-user CLS: 0.07

    0.07

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 673 ms

    673 ms

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

3 to fix53
  • Page weight: 11.4 MB in 386 requests

    11.4 MB

    Your homepage downloads 11.4 MB in 386 requests on a phone: fonts 6.8 MB (10), scripts 2.3 MB (126) and images 1.1 MB (96). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    FP10_banner_m.webp 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).

  • 10 images in older formats

    10 images (540 KiB) 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.

  • About 3.2 g of CO₂ per visit

    3.24 g

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

7 to fixGoogle 8489
  • Links must have discernible text (3 elements)

    Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

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

  • 2 text elements with low contrast

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

  • <svg> elements with an img or image role must have alternative text (1 element)

    <svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • 4 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 8581
  • Title is long (96 characters)

    Your title is 96 characters, so Google will cut it off around 60: “Dreame Türkiye Resmi Web Sitesi | Hayalinizdeki Yaşamı Güçlendirin – Dreame Türkiye Resmi…”.

  • Meta description is long (298 characters)

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • One H1 headline

    Your <h1> is empty.

  • 366 internal links, 82 external

    The homepage links to 366 pages on dreametech.com.tr and 82 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://dreametech.com.tr/.

  • Structured data in place

    Structured data found: OnlineStore.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://dreametech.com.tr/sitemap.xml.

AI search readiness

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

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://dreametech.com.tr/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 8 pages without an H1

    https://dreametech.com.tr/pages/kasim-buyuk-indirim-kampanyasi, https://dreametech.com.tr/collections/dreame-store, https://dreametech.com.tr/collections/robot-vacuums, https://dreametech.com.tr/products/dreame-x60-ultra-complete-robot-supurge, https://dreametech.com.tr/products/dreame-matrix-10-ultra-robot-supurge and https://dreametech.com.tr/products/dreame-l50-ultra-robot-supurge and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://dreametech.com.tr/collections/dreame-store, https://dreametech.com.tr/collections/robot-vacuums, https://dreametech.com.tr/products/dreame-x60-ultra-complete-robot-supurge, https://dreametech.com.tr/products/dreame-matrix-10-ultra-robot-supurge, https://dreametech.com.tr/products/dreame-l50-ultra-robot-supurge and https://dreametech.com.tr/products/dreame-aqua10-ultra-roller-complete-robot-supurge and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    8 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

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

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9697
  • 26 distorted images

    26 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 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 2,395 words of copy

    The homepage carries about 2,395 words of visible text.

4 checks passed
  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.

  • 37 other companies contacted

    Loading the homepage contacts 37 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 dreametech.com.tr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Blockify Fraud Filter · Uppromote Affiliate · Judge Me Reviews · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · Region Restrictions · Affliate By Secomapp · Restockrocket · cloudfront.net · goaffpro.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on dreametech.com.tr, including 22 speed issues, 4 SEO issues and 2 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