Website review, no card needed

1stly.com.ua logo

1stly.com.ua website review

Visit site (opens in a new tab)Reviewed 21 November 202647 issues · 87 checks

This review found 47 issues worth fixing on 1stly.com.ua, 21 of them high impact, across 87 checks. The most urgent: improve image delivery. 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 s1.2 sMay 30Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.4 s
Aug 1, 20261.5 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
123 ms96 msMay 30Nov 14111 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026116 ms
Jun 6, 2026113 ms
Jun 13, 2026112 ms
Jun 20, 2026111 ms
Jun 27, 2026108 ms
Jul 4, 2026106 ms
Jul 11, 2026107 ms
Jul 18, 2026109 ms
Jul 25, 2026113 ms
Aug 1, 2026120 ms
Aug 8, 2026113 ms
Aug 15, 2026111 ms
Aug 22, 2026104 ms
Aug 29, 2026103 ms
Sep 5, 2026103 ms
Sep 12, 2026109 ms
Sep 19, 2026108 ms
Sep 26, 2026111 ms
Oct 3, 2026107 ms
Oct 10, 2026101 ms
Oct 17, 2026102 ms
Oct 24, 202699 ms
Oct 31, 2026104 ms
Nov 7, 2026104 ms
Nov 14, 2026111 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 1stly.com.ua (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1stly.com.ua at 0.5 s0.5 s
  2. 1stly.com.ua at 1.0 s1.0 s
  3. 1stly.com.ua at 1.5 s1.5 s
  4. 1stly.com.ua at 2.0 s2.0 s
  5. 1stly.com.ua at 2.5 s2.5 s
  6. 1stly.com.ua at 3.0 s3.0 s
  7. 1stly.com.ua at 3.5 s3.5 s
  8. 1stly.com.ua at 4.0 s4.0 s

Speed

9 to fix28
  • Improve image delivery

    4.3 s · 4.3 MB

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

  • Render-blocking requests

    2.6 s

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

  • Reduce unused JavaScript

    1.1 s · 639 KiB

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

  • Mobile performance score: 28

    28/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 1.3 MB and 1.1 s of main-thread time.

  • Google Tag Manager adds 809 ms

    809 ms

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

  • Use efficient cache lifetimes

    600 ms · 201 KiB

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

  • Reduce unused CSS

    300 ms · 39 KiB

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

  • Facebook adds 258 ms

    258 ms

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

  • 13 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 9 KiB

    9 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 956 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

8 to fix100
  • Largest Contentful Paint: 21.8 s

    21.8 s

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

  • Time to Interactive: 22.5 s

    22.5 s

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

  • Cumulative Layout Shift: 0.505

    0.505

    The layout shifts by 0.505 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 6.8 s

    6.8 s

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

  • Total Blocking Time: 717 ms

    717 ms

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

  • Largest content (LCP) got 33% slower for real visitors

    +33%

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

  • 40 images without width and height

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • Tap response (INP) held steady for real visitors

    -6%

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

6 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.0 s

    2.0 s

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

  • Real-user INP: 90 ms

    90 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 620 ms

    620 ms

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

Images and page weight

5 to fix18
  • Page weight: 7.2 MB in 98 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 98 requests on a phone: images 5.6 MB (39), scripts 1.4 MB (34) and fonts 127 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.

  • 15 images far larger than shown

    2.0 MB

    15 images are downloaded at several times the size a phone draws them, for example BF26-03-banner.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 2.0 MB.

  • 28 images in older formats

    28 images (5.6 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.

  • 16 images below the first screen load straight away

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

  • About 2.1 g of CO₂ per visit

    2.05 g

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

Accessibility

9 to fixGoogle 6486
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Malformed lists

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

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

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

  • Zoom is disabled

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

  • 18 links without text

    18 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 34 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

4 to fixGoogle 9280
  • No H1 headline

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 2 links crawlers can't follow

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 55 internal links, 8 external

    The homepage links to 55 pages on 1stly.com.ua and 8 external pages.

4 checks passed
  • Meta description: 109 characters

    Your meta description is 109 characters: “. (066) 4-777-321 | ����������� ���, ���� ��� �������� ���������� ���������. ��������-������� ��������� 1STLY”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “1STLYskincare. ��������� ���������, ��� �� ������� ���������”.

  • 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://1stly.com.ua/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

  • No llms.txt

    There is no https://1stly.com.ua/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

Other pages

3 to fix86
  • 7 pages share 3 titles

    / and https://1stly.com.ua/all/c-0.html all use the title “1STLYskincare. ��������� ���������, ��� �� ������� ���������”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://1stly.com.ua/oblichchja/c-375.html and https://1stly.com.ua/lico/c-375.html use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://1stly.com.ua/spivpracja/info-47.html has no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages with very little text

    https://1stly.com.ua/tilo/c-520.html, https://1stly.com.ua/volossja/c-379.html, https://1stly.com.ua/pidlitki/c-579.html, https://1stly.com.ua/nabory/c-572.html, https://1stly.com.ua/spivpracja/info-47.html and https://1stly.com.ua/nabori/c-572.html and 5 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.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 15 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 58 words

    The homepage has only about 58 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
  • 8 short forms

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

  • Analytics in place

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

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.

  • 6 cookies set on arrival

    6

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

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 1stly.com.ua, 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
Analytics
Google Analytics | Google Tag Manager
Hosting
Internet Invest, Ltd.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on 1stly.com.ua, including 17 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

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