Website review, no card needed

millyandmolly.gr logo

millyandmolly.gr website review

Visit site (opens in a new tab)Reviewed 20 November 202628 issues · 81 checks

This review found 28 issues worth fixing on millyandmolly.gr, 10 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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
922 ms685 msMay 30Nov 14712 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026889 ms
Jun 6, 2026883 ms
Jul 11, 2026784 ms
Jul 18, 2026780 ms
Jul 25, 2026810 ms
Aug 1, 2026807 ms
Aug 8, 2026874 ms
Aug 15, 2026873 ms
Aug 22, 2026874 ms
Aug 29, 2026895 ms
Sep 5, 2026869 ms
Sep 12, 2026864 ms
Sep 19, 2026809 ms
Sep 26, 2026807 ms
Oct 3, 2026818 ms
Oct 10, 2026802 ms
Oct 17, 2026841 ms
Oct 24, 2026767 ms
Oct 31, 2026736 ms
Nov 7, 2026742 ms
Nov 14, 2026712 ms
Real-visitor tap response (INP)75th percentile, phones
91 ms68 msMay 30Nov 1479 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202684 ms
Jun 6, 202680 ms
Jul 11, 202673 ms
Jul 18, 202671 ms
Jul 25, 202677 ms
Aug 1, 202678 ms
Aug 8, 202682 ms
Aug 15, 202688 ms
Aug 22, 202685 ms
Aug 29, 202681 ms
Sep 5, 202681 ms
Sep 12, 202679 ms
Sep 19, 202677 ms
Sep 26, 202678 ms
Oct 3, 202679 ms
Oct 10, 202678 ms
Oct 17, 202683 ms
Oct 24, 202681 ms
Oct 31, 202679 ms
Nov 7, 202680 ms
Nov 14, 202679 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 millyandmolly.gr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. millyandmolly.gr at 0.9 s0.9 s
  2. millyandmolly.gr at 1.8 s1.8 s
  3. millyandmolly.gr at 2.7 s2.7 s
  4. millyandmolly.gr at 3.6 s3.6 s
  5. millyandmolly.gr at 4.5 s4.5 s
  6. millyandmolly.gr at 5.5 s5.5 s
  7. millyandmolly.gr at 6.4 s6.4 s
  8. millyandmolly.gr at 7.3 s7.3 s

Speed

6 to fix64
  • Render-blocking requests

    1.4 s

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

  • Reduce unused JavaScript

    1.1 s · 237 KiB

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

  • Improve image delivery

    250 ms · 899 KiB

    24 images could be 899 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Mobile performance score: 64

    64/100

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

  • Font display

    950 ms

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

  • 1,773 HTML elements

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

  • Reduce unused CSS

    200 ms · 59 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and skroutz.gr and others), adding 417 KiB and 179 ms of main-thread time.

  • Use efficient cache lifetimes

    126 KiB

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

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    12 KiB

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 117 ms

    117 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 16.4 s

    16.4 s

    Your largest element takes 16.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: 17.3 s

    17.3 s

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

  • Speed Index: 9.3 s

    9.3 s

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

  • 31 images without width and height

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Tap response (INP) held steady for real visitors

    -3%

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

9 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.7 s

    0.7 s

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

  • Real-user INP: 80 ms

    80 ms

    Real visitors wait 80 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: 426 ms

    426 ms

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

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

    -18%

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

  • Cumulative Layout Shift: 0.034

    0.034

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

  • Total Blocking Time: 45 ms

    45 ms

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

Images and page weight

3 to fix53
  • Page weight: 5.1 MB in 129 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 129 requests on a phone: images 4.3 MB (109), scripts 424 KiB (7) and fonts 363 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 40 images in older formats

    40 images (3.4 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.

  • 15 images below the first screen load straight away

    15 images further down the page (928 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.45 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.45 g of CO₂e: 174.6 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

4 to fixGoogle 9794
  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 8 elements on the page fail 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 155 images in the HTML carry an alt attribute.

  • 48 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: 48 passed and 3 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 9283
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No canonical URL

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), 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.

  • 335 internal links, 6 external

    The homepage links to 335 pages on millyandmolly.gr and 6 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “ΣΑΣ ΠΡΟΤΕΙΝΟΥΜΕ”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Παιδικά Ρούχα Πάτρα, Milly & Molly”.

  • Structured data in place

    Structured data found: WebSite.

  • 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.millyandmolly.gr/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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://www.millyandmolly.gr/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.

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (174 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix63
  • 1 linked page is broken

    Your homepage links to https://www.millyandmolly.gr/marasil, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 3 pages share a title

    /, https://www.millyandmolly.gr/%CE%B1%CF%81%CF%87%CE%B9%CE%BA%CE%AE and https://www.millyandmolly.gr/action/1962/set_lang all use the title “Παιδικά Ρούχα Πάτρα, Milly & Molly”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://www.millyandmolly.gr/%CE%B5%CF%84%CE%B1%CE%B9%CF%81%CE%AF%CE%B1, https://www.millyandmolly.gr/%CE%B5%CF%80%CE%B9%CE%BA%CE%BF%CE%B9%CE%BD%CF%89%CE%BD%CE%AF%CE%B1, https://www.millyandmolly.gr/gallery, https://www.millyandmolly.gr/newsletter, https://www.millyandmolly.gr/%CE%B1%CF%81%CF%87%CE%B9%CE%BA%CE%AE and https://www.millyandmolly.gr/start and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages with very little text

    https://www.millyandmolly.gr/%CE%B5%CF%84%CE%B1%CE%B9%CF%81%CE%AF%CE%B1, https://www.millyandmolly.gr/%CE%B5%CF%80%CE%B9%CE%BA%CE%BF%CE%B9%CE%BD%CF%89%CE%BD%CE%AF%CE%B1, https://www.millyandmolly.gr/gallery, https://www.millyandmolly.gr/newsletter and https://www.millyandmolly.gr/ikks 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 20 found) and read each the way a search engine does.

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

Google 96100
  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    42 of 50 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 155 words

    The homepage has only about 155 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Login / Sign Up” and “SHOP NOW”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies, 2 of them by other companies (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.

  • 5 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics
Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on millyandmolly.gr, including 11 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