Website review, no card needed

motomax.com.tr logo

motomax.com.tr website review

Visit site (opens in a new tab)Reviewed 19 October 202641 issues · 86 checks

This review found 41 issues worth fixing on motomax.com.tr, 15 of them high impact, across 86 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

Real-visitor load time (LCP)75th percentile, phones
1.8 s865 msApr 25Oct 10973 ms
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.7 s
May 2, 20261.7 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.4 s
Sep 26, 20261.0 s
Oct 3, 2026994 ms
Oct 10, 2026973 ms
Real-visitor tap response (INP)75th percentile, phones
121 ms105 msApr 25Oct 10115 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026109 ms
May 2, 2026108 ms
May 9, 2026107 ms
May 16, 2026107 ms
May 23, 2026108 ms
May 30, 2026108 ms
Jun 6, 2026109 ms
Jun 13, 2026111 ms
Jun 20, 2026111 ms
Jun 27, 2026112 ms
Jul 4, 2026113 ms
Jul 11, 2026112 ms
Jul 18, 2026112 ms
Jul 25, 2026112 ms
Aug 1, 2026112 ms
Aug 8, 2026114 ms
Aug 15, 2026115 ms
Aug 22, 2026116 ms
Aug 29, 2026117 ms
Sep 5, 2026117 ms
Sep 12, 2026118 ms
Sep 19, 2026119 ms
Sep 26, 2026116 ms
Oct 3, 2026116 ms
Oct 10, 2026115 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 motomax.com.tr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. motomax.com.tr at 1.2 s1.2 s
  2. motomax.com.tr at 2.4 s2.4 s
  3. motomax.com.tr at 3.5 s3.5 s
  4. motomax.com.tr at 4.7 s4.7 s
  5. motomax.com.tr at 5.9 s5.9 s
  6. motomax.com.tr at 7.1 s7.1 s
  7. motomax.com.tr at 8.3 s8.3 s
  8. motomax.com.tr at 9.4 s9.4 s

Speed

10 to fix54
  • Reduce unused JavaScript

    3.5 s · 719 KiB

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

  • Use efficient cache lifetimes

    1.4 s · 455 KiB

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

  • Render-blocking requests

    1.3 s

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

  • Improve image delivery

    450 ms · 2.7 MB

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

  • 8 third-party services on the page

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

  • Mobile performance score: 54

    54/100

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

  • Google Tag Manager adds 444 ms

    444 ms

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

  • Main-thread work: 3.5 s

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

  • 2,949 HTML elements

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

  • embedsocial.com adds 108 ms

    108 ms

    embedsocial.com costs a phone 108 ms of main-thread work and 836 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

    250 ms · 30 KiB

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

  • 12 long tasks on the main thread

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

  • Minify CSS

    150 ms · 4 KiB

    4 KiB could be saved by minifying CSS.

  • Reduce unused CSS

    43 KiB

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

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

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

    191 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 27.0 s

    27.0 s

    Your largest element takes 27.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “İş Başvuru”.

  • Time to Interactive: 29.4 s

    29.4 s

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

  • Speed Index: 14.4 s

    14.4 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Total Blocking Time: 314 ms

    314 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 121 ms

    121 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 458 ms

    458 ms

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

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

    -41%

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

  • Cumulative Layout Shift: 0.019

    0.019

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

Images and page weight

5 to fix18
  • Page weight: 15.3 MB in 287 requests

    15.3 MB

    Your homepage downloads 15.3 MB in 287 requests on a phone: images 13.3 MB (207), scripts 1.5 MB (33) and fonts 241 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 15 images far larger than shown

    2.3 MB

    15 images are downloaded at several times the size a phone draws them, for example herman-tr-1.jpg at 1,025 px wide, shown at 21 px. Resized copies would save about 2.3 MB.

  • 1 image over 500 KB

    tr_img_1_1688.png weighs 595 KiB. On a phone connection a single image that size takes seconds.

  • 40 images in older formats

    40 images (6.8 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.

  • 14 images below the first screen load straight away

    14 images further down the page (2.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.3 g of CO₂ per visit

    4.34 g

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

Accessibility

10 to fixGoogle 8688
  • 21 tap targets too small

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

  • Malformed lists

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

  • 4 images without alt text

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

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 8 links without text

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

  • Alternative text of images should not be repeated as text (13 elements)

    Alternative text of images should not be repeated as text: 13 elements on the page fail this check, rated minor by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (8 elements)

    Headings should not be empty: 8 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

2 to fixGoogle 10083
  • No H1 headline

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

  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “Motomax - En İyi Motosiklet Ekipmanları | Kask Mont Pantolon Eldiven Bot”.

  • 503 internal links, 36 external

    The homepage links to 503 pages on motomax.com.tr and 36 external pages.

6 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Türkiye'nin en zengin motosiklet aksesuarları mağazası Motomax'ta en iyi motosiklet ekipmanları satılır. Kaliteli motor…”.

  • Canonical URL set

    The canonical URL is https://www.motomax.com.tr/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.motomax.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,603 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.motomax.com.tr/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9291
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Unexpected token '.'”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • 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.

  • Local business without LocalBusiness data

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

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

  • 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 797 words of copy

    The homepage carries about 797 words of visible text.

3 checks passed
  • 3 short forms

    3 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 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.

  • 21 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2024.

Stack

Framework
jQuery
Analytics
Google 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 41 issues on motomax.com.tr, including 16 speed issues, 2 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