Website review, no card needed

wigmond.ro logo

wigmond.ro website review

Visit site (opens in a new tab)Reviewed 20 November 202640 issues · 82 checks

This review found 40 issues worth fixing on wigmond.ro, 18 of them high impact, across 82 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
2.5 s1.7 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Nov 7, 20261.8 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
265 ms106 msMay 30Nov 14219 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026124 ms
Jun 6, 2026128 ms
Jun 13, 2026138 ms
Jun 20, 2026170 ms
Jun 27, 2026195 ms
Jul 4, 2026208 ms
Jul 11, 2026208 ms
Jul 18, 2026203 ms
Jul 25, 2026204 ms
Aug 1, 2026209 ms
Aug 8, 2026223 ms
Aug 15, 2026237 ms
Aug 22, 2026244 ms
Aug 29, 2026247 ms
Sep 5, 2026242 ms
Sep 12, 2026236 ms
Sep 19, 2026230 ms
Sep 26, 2026225 ms
Oct 3, 2026227 ms
Oct 10, 2026228 ms
Oct 17, 2026224 ms
Oct 24, 2026229 ms
Oct 31, 2026233 ms
Nov 7, 2026219 ms
Nov 14, 2026219 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 wigmond.ro (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wigmond.ro at 0.8 s0.8 s
  2. wigmond.ro at 1.7 s1.7 s
  3. wigmond.ro at 2.5 s2.5 s
  4. wigmond.ro at 3.4 s3.4 s
  5. wigmond.ro at 4.2 s4.2 s
  6. wigmond.ro at 5.1 s5.1 s
  7. wigmond.ro at 5.9 s5.9 s
  8. wigmond.ro at 6.8 s6.8 s

Speed

9 to fix49
  • Improve image delivery

    17.4 s · 14.5 MB

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

  • Use efficient cache lifetimes

    6.8 s · 7.5 MB

    116 files are served with short cache lifetimes, so returning visitors download them again (7.5 MB).

  • Reduce unused JavaScript

    2.3 s · 661 KiB

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

  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 49

    49/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google CDN and Cloudflare and others), adding 1.0 MB and 555 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 97 KiB

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

  • Google Tag Manager adds 427 ms

    427 ms

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

  • Google CDN adds 108 ms

    108 ms

    Google CDN costs a phone 108 ms of main-thread work and 353 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.

  • Minify JavaScript

    150 ms · 31 KiB

    31 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 24 KiB

    24 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    150 ms · 17 KiB

    Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 9 long tasks on the main thread

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

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

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

  • Server response: 133 ms

    133 ms

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

Core Web Vitals

11 to fix33
  • 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.

  • Real-user CLS: 0.46

    0.46

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

  • Largest Contentful Paint: 26.3 s

    26.3 s

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

  • Time to Interactive: 61.2 s

    61.2 s

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

  • Speed Index: 13.5 s

    13.5 s

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

  • Real-user INP: 237 ms

    237 ms

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

  • Tap response (INP) got 74% slower for real visitors

    +74%

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

  • Cumulative Layout Shift: 0.225

    0.225

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Total Blocking Time: 221 ms

    221 ms

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

  • 2 images without width and height

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

4 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 744 ms

    744 ms

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

  • Largest content (LCP) got 21% faster for real visitors

    -21%

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

Images and page weight

5 to fix14
  • Page weight: 16.8 MB in 148 requests

    16.8 MB

    Your homepage downloads 16.8 MB in 148 requests on a phone: images 15.1 MB (33), scripts 1.4 MB (60) and stylesheets 198 KiB (41). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 9.3 MB together. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    4.3 MB

    7 images are downloaded at several times the size a phone draws them, for example 186c11cf9f86a747336e_Nature Escape Site.png at 1,935 px wide, shown at 390 px. Resized copies would save about 4.3 MB.

  • 12 images in older formats

    12 images (10.5 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.

  • An image on the first screen is lazy-loaded

    186c11cf9f86a747336e_Nature Escape Site.png 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).

  • About 4.8 g of CO₂ per visit

    4.77 g

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

Accessibility

5 to fixGoogle 8492
  • 8 buttons without a name

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

  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

  • 7 text elements with low contrast

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

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • No H1 headline

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

  • Structured data has 1 problem

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 91 internal links, 3 external

    The homepage links to 91 pages on wigmond.ro and 3 external pages.

5 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Comandă online produse pt. unghii, coafura, cosmetică, unghii tehnice, manichiură/pedichiură, unghii cu gel. Totul pt. …”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Wigmond.ro - coafură, cosmetică, manichiură, pedichiură”.

  • Canonical URL set

    The canonical URL is https://www.wigmond.ro/.

  • 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://www.wigmond.ro/1_index_sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    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.

  • No llms.txt

    There is no https://www.wigmond.ro/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

2 to fix90
  • 3 pages without a meta description

    https://www.wigmond.ro/blog, https://www.wigmond.ro/module/tvcmsproductcompare/productcomparelist and https://www.wigmond.ro/615-promotiile-toamnei-2026 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.wigmond.ro/promotii, https://www.wigmond.ro/contact, https://www.wigmond.ro/module/tvcmsproductcompare/productcomparelist, https://www.wigmond.ro/615-promotiile-toamnei-2026, https://www.wigmond.ro/16-manichiura-pedichiura and https://www.wigmond.ro/118-coafura and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://www.wigmond.ro/promotii, https://www.wigmond.ro/blog, https://www.wigmond.ro/615-promotiile-toamnei-2026, https://www.wigmond.ro/118-coafura, https://www.wigmond.ro/110-produse-pentru-epilat and https://www.wigmond.ro/285-make-up and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 60 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.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 28 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

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

2 to fix79
  • 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.

  • Only about 128 words

    The homepage has only about 128 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.

5 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “shop now” and “Shop Now”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and 8 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 3 cookies set on arrival

    3

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

  • 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 wigmond.ro, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

E-commerce
PrestaShop
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

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 wigmond.ro, including 20 speed issues, 3 SEO issues and 2 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