Programmable

Website review, no card needed

woolona.mk logo

woolona.mk website review

Visit site (opens in a new tab)Reviewed 11 November 202621 issues · 68 checks

This review found 21 issues worth fixing on woolona.mk, 7 of them high impact, across 68 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

Site score

83B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
925 ms597 msJul 18Nov 7635 ms
Show as table
DateReal-visitor load time (LCP)
Jul 18, 2026673 ms
Jul 25, 2026640 ms
Aug 1, 2026688 ms
Aug 8, 2026753 ms
Aug 15, 2026760 ms
Aug 22, 2026828 ms
Aug 29, 2026832 ms
Sep 5, 2026872 ms
Sep 12, 2026887 ms
Sep 19, 2026881 ms
Sep 26, 2026773 ms
Oct 3, 2026777 ms
Oct 10, 2026746 ms
Oct 17, 2026704 ms
Oct 24, 2026682 ms
Oct 31, 2026640 ms
Nov 7, 2026635 ms
Real-visitor tap response (INP)75th percentile, phones
89 ms80 msSep 12Nov 788 ms
Show as table
DateReal-visitor tap response (INP)
Sep 12, 202681 ms
Sep 26, 202685 ms
Oct 3, 202687 ms
Oct 10, 202686 ms
Oct 17, 202682 ms
Oct 24, 202686 ms
Oct 31, 202687 ms
Nov 7, 202688 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

woolona.mk (opens in a new tab)
Full-page screenshot of woolona.mk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. woolona.mk at 0.4 s0.4 s
  2. woolona.mk at 0.8 s0.8 s
  3. woolona.mk at 1.1 s1.1 s
  4. woolona.mk at 1.5 s1.5 s
  5. woolona.mk at 1.9 s1.9 s
  6. woolona.mk at 2.3 s2.3 s
  7. woolona.mk at 2.6 s2.6 s
  8. woolona.mk at 3.0 s3.0 s

Speed

3 to fix78

  • Improve image delivery

    1.1 s · 422 KiB

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

  • Mobile performance score: 78

    78/100

    Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    450 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Reduce unused JavaScript

    47 KiB

    About 47 KiB of JavaScript is downloaded but never used on this page.

  • 3 third-party services on the page

    3 third-party services load with your homepage (langshop.app, nfcube.com and Shopify), adding 99 KiB and 28 ms of main-thread time.

  • Use efficient cache lifetimes

    8 KiB

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

  • 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: 0.7 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

2 to fix100

  • Largest Contentful Paint: 5.4 s

    5.4 s

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

  • Time to Interactive: 5.6 s

    5.6 s

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

10 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: 0.9 s

    0.9 s

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

  • Real-user INP: 83 ms

    83 ms

    Real visitors wait 83 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: 0.6 s

    0.6 s

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

  • Real-user TTFB: 208 ms

    208 ms

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

  • Cumulative Layout Shift: 0.084

    0.084

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

  • Speed Index: 2.1 s

    2.1 s

    Visually, the page fills in at 2.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix81

  • Page weight: 2.3 MB in 225 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 225 requests on a phone: images 1.1 MB (34), other files 985 KiB (147) and scripts 180 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    volena_obleka_merino_volna_base_layer_aktiven_vesh_obleka_za is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (35 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.65 g

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

1 checks passed

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 9798

  • 17 text elements with low contrast

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

2 checks passed

  • Every image has alt text

    All 35 images in the HTML carry an alt attribute.

  • 50 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: 50 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095

  • One H1 headline

    Your <h1> is empty.

  • 63 internal links, 4 external

    The homepage links to 63 pages on woolona.mk and 4 external pages.

7 checks passed

  • Meta description: 121 characters

    Your meta description is 121 characters: “100% австралиска мерино волна облека за скијање, планина, фитнес, суви топли, лето лади, зиме грее, без мирис при потењ…”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Woolona мерино свет – Woolona.mk”.

  • Canonical URL set

    The canonical URL is https://woolona.mk/.

  • 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://woolona.mk/sitemap.xml.

AI search readiness

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

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

  • llms.txt published

    The site publishes https://woolona.mk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix63

  • 1 page without a title

    https://woolona.mk/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://woolona.mk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 11 pages without a meta description

    https://woolona.mk/collections/%D0%BC%D0%B0%D1%88%D0%BA%D0%B8/base-layer, https://woolona.mk/collections/%D0%BC%D0%B0%D1%88%D0%BA%D0%B8/Mid-Layer, https://woolona.mk/collections/%D0%BC%D0%B0%D1%88%D0%BA%D0%B8/seamless, https://woolona.mk/collections/%D0%B6%D0%B5%D0%BD%D1%81%D0%BA%D0%B8/Base-Layer, https://woolona.mk/collections/%D0%B6%D0%B5%D0%BD%D1%81%D0%BA%D0%B8/Mid-Layer and https://woolona.mk/collections/%D0%B6%D0%B5%D0%BD%D1%81%D0%BA%D0%B8/Seamless and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 links to non-canonical URLs

    Your homepage links to 10 pages by a URL that isn't their canonical one, for example https://woolona.mk/collections/%D0%BC%D0%B0%D1%88%D0%BA%D0%B8/base-layer, whose canonical is https://woolona.mk/collections/%d0%bc%d0%b0%d1%88%d0%ba%d0%b8/base-layer. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://woolona.mk/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://woolona.mk/collections/%D0%B4%D0%B5%D1%82%D1%81%D0%BA%D0%B8, https://woolona.mk/pages/perenje-merino-volna, https://woolona.mk/pages/merino-volna-ne-chesha, https://woolona.mk/pages/istorija-na-merino-aktiven-vesh and https://woolona.mk/pages/odrzliv-merino-proizvod 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.

  • 3 pages slow to respond

    https://woolona.mk/collections/%D0%BC%D0%B0%D1%88%D0%BA%D0%B8/seamless, https://woolona.mk/collections/%D0%B6%D0%B5%D0%BD%D1%81%D0%BA%D0%B8/Base-Layer and https://woolona.mk/customer_authentication/redirect took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 9693

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Error from API: undefined”.

2 checks passed

  • Tap targets are thumb-sized

    25 of 27 tappable elements near the top are at least 24 px.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 104 words

    The homepage has only about 104 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 short forms

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 7 other companies contacted

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

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

langshop.app · nfcube.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

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 21 issues on woolona.mk, including 5 speed issues, 1 SEO issue 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