Website review, no card needed
omtec.com.tr website review
Visit site (opens in a new tab)Reviewed 23 October 202640 issues · 82 checks
This review found 40 issues worth fixing on omtec.com.tr, 17 of them high impact, across 82 checks. The most urgent: page weight: 25.0 MB in 136 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73C- #70,761 of 95,228 reviewed websitesbeats 22%
- #42,090 of 51,304 online storesbeats 15%
- #39,221 of 46,417 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.3 s |
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 131 ms |
| May 9, 2026 | 129 ms |
| May 16, 2026 | 132 ms |
| May 23, 2026 | 123 ms |
| May 30, 2026 | 122 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 123 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 131 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 125 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 122 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 130 ms |
| Sep 19, 2026 | 134 ms |
| Sep 26, 2026 | 132 ms |
| Oct 3, 2026 | 130 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 139 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
Speed
Render-blocking requests
2.0 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 54). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.8 s
A phone's processor spends 6.8 s on main-thread work while loading, 5.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 2.2 s. During a long task the page ignores taps.
6 third-party services on the page
6 third-party services load with your homepage (Shopify, Hexton and Google CDN and others), adding 289 KiB and 745 ms of main-thread time.
Shopify adds 649 ms
649 msShopify costs a phone 649 ms of main-thread work and 102 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.
Reduce unused CSS
450 ms · 121 KiBAbout 121 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
350 ms · 65 KiB3 images could be 65 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Reduce unused JavaScript
173 KiBAbout 173 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
31 KiB5 files are served with short cache lifetimes, so returning visitors download them again (31 KiB).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Total Blocking Time: 2.4 s
2.4 sScripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 9.2 s
9.2 sThe page becomes fully interactive after 9.2 s. Good is under 3.8 s.
Largest Contentful Paint: 4.6 s
4.6 sYour largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 131 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 142 ms
142 msReal visitors wait 142 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 492 ms
492 msReal visitors wait 492 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.3 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 25.0 MB in 136 requests
25.0 MBYour homepage downloads 25.0 MB in 136 requests on a phone: media 23.3 MB (2), other files 682 KiB (71) and scripts 524 KiB (38). Under 2 MB keeps phones on slow connections fast.
About 7.1 g of CO₂ per visit
7.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.09 g of CO₂e: 851.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (22 characters)
Your title is only 22 characters: “Omtec Auto Accessories”. Between 30 and 65 characters leaves room to say what you do and for whom.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
201 internal links, 4 external
The homepage links to 201 pages on omtec.com.tr and 4 external pages.
6 checks passed
Meta description: 112 characters
Your meta description is 112 characters: “Omtec Oto Aksesuar - Araç İçi Aksesuarlar, Araç Dışı Aksesuarlar, Paslanmaz Çelik, ABS Krom, Karbon Aksesuarlar.”.
Canonical URL set
The canonical URL is https://omtec.com.tr/en.
Structured data in place
Structured data found: 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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://omtec.com.tr/sitemap.xml.
AI search readiness
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.
3 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 (607 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://omtec.com.tr/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://omtec.com.tr/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://omtec.com.tr/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 pages without a meta description
https://omtec.com.tr/en/collections/inner-accessories, https://omtec.com.tr/en/collections/exterior-accessories, https://omtec.com.tr/en/collections/ceiling-supports, https://omtec.com.tr/en/collections/aesthetic-accessories, https://omtec.com.tr/en/collections/camping-accessories and https://omtec.com.tr/en/collections/steps and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://omtec.com.tr/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://omtec.com.tr/customer_authentication/redirect took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 89 found) and read each the way a search engine does.
3 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.
Best practices
4 small tap targets
4 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 185 words
The homepage has only about 185 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “CONTACT” and “Contact”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 omtec.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
- jQuery
- E-commerce
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on omtec.com.tr, including 16 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.