Website review, no card needed
tugba.com website review
Visit site (opens in a new tab)Reviewed 3 November 202623 issues · 68 checks
This review found 23 issues worth fixing on tugba.com, 5 of them high impact, across 68 checks. The most urgent: render-blocking 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
87B- #6,861 of 96,363 reviewed websitesbeats 90%
- #3,840 of 52,193 online storesbeats 89%
- #3,724 of 47,279 Shopify storesbeats 88%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.5 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 81
81/100Your mobile performance score is 81. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 265 KiBAbout 265 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
2,449 HTML elements
The page has 2,449 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 44 ms
44 msShopify costs a phone 44 ms of main-thread work and 368 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
150 ms · 12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
116 KiB7 images could be 116 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
6 third-party services on the page
6 third-party services load with your homepage (Shopify, aliyuncs.com and robinpro.gallery and others), adding 598 KiB and 46 ms of main-thread time.
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.
Use efficient cache lifetimes
4 KiB4 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 290 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.3 s
4.3 sYour largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Time to Interactive: 4.3 s
4.3 sThe page becomes fully interactive after 4.3 s. Good is under 3.8 s.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.6 MB in 189 requests
2.6 MBYour homepage downloads 2.6 MB in 189 requests on a phone: images 1.0 MB (36), other files 721 KiB (74) and scripts 520 KiB (49). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (106 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 0.7 g of CO₂ per visit
0.73 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.73 g of CO₂e: 87.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (215 characters)
Your meta description is 215 characters; Google truncates after about 160, so the end of your pitch is cut.
220 internal links, 12 external
The homepage links to 220 pages on tugba.com and 12 external pages.
7 checks passed
One H1 headline
Your main headline reads: “TUĞBA Modest Fashion”.
Title: 36 characters
Your title is a healthy 36 characters: “Tuğba | Hijab Clothing Brand | TUĞBA”.
Canonical URL set
The canonical URL is https://tugba.com/en.
Structured data in place
Structured data found: Organization 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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://tugba.com/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,264 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://tugba.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages hidden from search
https://tugba.com/en/pages/on-bilgilendirme-formu and https://tugba.com/en/pages/mesafeli-satis-sozlesmesi are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
1 page without a meta description
https://tugba.com/en/collections/yeni-gelenler-dis-giyim has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://tugba.com/en/pages/ilham-panosu and https://tugba.com/en/collections/kadin-giyim have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 110 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Only about 246 words
The homepage has only about 246 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.
3 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Call Us 0850 302 64 64”, “Write to Us Send your request” and “Order Tracking View your orders”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
9 other companies contacted
Loading the homepage contacts 9 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 tugba.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on tugba.com, including 9 speed issues, 1 SEO issue and 4 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.