tradeline.ge website review

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

Google Tag Manager costs a phone 1.8 s of main-thread work and 903 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

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

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

About 528 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.

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

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

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

reddit costs a phone 357 ms of main-thread work and 35 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.

56 KiB could be saved by minifying JavaScript.

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

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

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

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

5 KiB could be saved by minifying CSS.

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 visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “06.11 30% ფასდაკლება თავის მოვლის სრულ კოლექციაზე პრომო კოდ…”.

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

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

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

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

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

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

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

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

Your homepage downloads 7.2 MB in 346 requests on a phone: images 4.0 MB (161), scripts 1.9 MB (90) and fonts 734 KiB (6). Under 2 MB keeps phones on slow connections fast.

15 images are downloaded at several times the size a phone draws them, for example eja-პლედი-140x180-სმ-cm.webp at 675 px wide, shown at 168 px. Resized copies would save about 722 KiB.

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

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

Your title is 104 characters, so Google will cut it off around 60: “Dressup.ge - ონლაინ მაღაზია | ტანსაცმელი, ფეხსაცმელი, აქსესუარები | საერთაშორისო ბრენდები…”.

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

9 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 2,196 pages on tradeline.ge and 0 external pages.

A phone browser shows 250 words, but the HTML your server sends has only 14. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to /ka/module/iqitwishlist/view, which answers with an error. Visitors hit a dead end and search engines drop it.

/ka/30164-30off-entire-self-care has no meta description, so Google writes the search snippet from whatever text it finds.

/ka/brands, /ka/30164-30off-entire-self-care, /ka/content/1-%E1%83%A2%E1%83%A0%E1%83%90%E1%83%9C%E1%83%A1%E1%83%9E%E1%83%9D%E1%83%A0%E1%83%A2%E1%83%98%E1%83%A0%E1%83%94%E1%83%91%E1%83%90, /ka/74-qali, /ka/75-katsi and /ka/76-bavshvi and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

/ka/brands, /ka/30164-30off-entire-self-care, /ka/content/1-%E1%83%A2%E1%83%A0%E1%83%90%E1%83%9C%E1%83%A1%E1%83%9E%E1%83%9D%E1%83%A0%E1%83%A2%E1%83%98%E1%83%A0%E1%83%94%E1%83%91%E1%83%90, /ka/74-qali, /ka/75-katsi and /ka/76-bavshvi and 7 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/ka/74-qali, /ka/content/116-tavis-movla, /ka/content/111-sakhli, /ka/new-products, /ka/10-kalis-fexsacmeli and /ka/1711-%E1%83%A5%E1%83%90%E1%83%9A%E1%83%98%E1%83%A1-%E1%83%97%E1%83%94%E1%83%97%E1%83%A0%E1%83%94%E1%83%A3%E1%83%9A%E1%83%98 took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187214843&tm=gtm002&Ver=2&mid=631f12ac-68d6-41cb-808f-7fd87a50886d&bo=1&sid=7f4efa00d95711f1a596cdc7322a4f82&vid=7f4f08f0d95711f19757538c2764cbac&vids=1&msclkid=N&gtm_.

24 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Cannot set properties of undefined (setting 'id')”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

1 link from your homepage to your own site is broken, for example https://dressup.ge/ka/module/iqitwishlist/view (404).

http://tradeline.ge does not redirect to https, so some visitors land on the insecure version.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://tradeline.ge goes through 3 redirects before the homepage loads.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

dressup.ge has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

The homepage carries about 250 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

tradeline.ge has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 23 cookies, 2 of them by other companies (measured from a US location before any click).

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.

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