Website review, no card needed

1ashop.ro logo

1ashop.ro website review

Visit site (opens in a new tab)Reviewed 31 October 202635 issues · 98 checks

This review found 35 issues worth fixing on 1ashop.ro, 13 of them high impact, across 98 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
3.0 s2.6 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.8 s
May 16, 20262.8 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.8 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.7 s
Aug 22, 20262.8 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
438 ms184 msMay 9Oct 24396 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026213 ms
May 16, 2026220 ms
May 23, 2026230 ms
May 30, 2026239 ms
Jun 6, 2026241 ms
Jun 13, 2026255 ms
Jun 20, 2026271 ms
Jun 27, 2026289 ms
Jul 4, 2026310 ms
Jul 11, 2026324 ms
Jul 18, 2026331 ms
Jul 25, 2026333 ms
Aug 1, 2026350 ms
Aug 8, 2026363 ms
Aug 15, 2026373 ms
Aug 22, 2026386 ms
Aug 29, 2026379 ms
Sep 5, 2026372 ms
Sep 12, 2026363 ms
Sep 19, 2026384 ms
Sep 26, 2026392 ms
Oct 3, 2026397 ms
Oct 10, 2026409 ms
Oct 17, 2026396 ms
Oct 24, 2026396 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 1ashop.ro (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1ashop.ro at 0.8 s0.8 s
  2. 1ashop.ro at 1.6 s1.6 s
  3. 1ashop.ro at 2.4 s2.4 s
  4. 1ashop.ro at 3.2 s3.2 s
  5. 1ashop.ro at 4.0 s4.0 s
  6. 1ashop.ro at 4.8 s4.8 s
  7. 1ashop.ro at 5.6 s5.6 s
  8. 1ashop.ro at 6.4 s6.4 s

1ashop.ro does not allow embedding, so this is Google's rendering of the page.

Speed

6 to fix63
  • Render-blocking requests

    1.8 s

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

  • Main-thread work: 4.7 s

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

  • 4,094 HTML elements

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

  • Mobile performance score: 63

    63/100

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

  • Improve image delivery

    100 ms · 883 KiB

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

  • Reduce unused JavaScript

    300 ms · 106 KiB

    About 106 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and willdesk.com and others), adding 499 KiB and 274 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 37 KiB

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

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    30 KiB

    About 30 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    18 KiB

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

  • Forced reflow

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 75 ms

    75 ms

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

Core Web Vitals

9 to fix67
  • 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 LCP: 5.3 s

    5.3 s

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

  • Largest Contentful Paint: 13.6 s

    13.6 s

    Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “CASUALNIKI - ÎNCĂLȚĂMINTE BĂRBĂTEASCĂ”.

  • Time to Interactive: 13.8 s

    13.8 s

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

  • Speed Index: 8.6 s

    8.6 s

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

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

    +83%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

5 checks passed
  • Real-user INP: 192 ms

    192 ms

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

  • Real-user CLS: 0.01

    0.01

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

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

  • Total Blocking Time: 73 ms

    73 ms

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

  • Cumulative Layout Shift: 0.035

    0.035

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

Images and page weight

1 to fix85
  • Page weight: 2.8 MB in 241 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 241 requests on a phone: images 1.1 MB (14), other files 885 KiB (84) and scripts 657 KiB (104). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.81 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8793
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 84 text elements with low contrast

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

5 to fixGoogle 8573
  • No meta description

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

  • Title is short (9 characters)

    Your title is only 9 characters: “1Ashop.ro”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • One H1 headline

    Your <h1> is empty.

  • 102 internal links, 3 external

    The homepage links to 102 pages on 1ashop.ro and 3 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.1ashop.ro/.

  • Structured data in place

    Structured data found: Organization and 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.1ashop.ro/sitemap.xml.

AI search readiness

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 11 pages without a meta description

    /collections/shoes-winter, /collections/shoes-summer, /collections/incaltaminte-barbati, /collections/incaltaminte-femei, /collections/haina-de-iarna and /collections/haina-de-vara and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    /collections/sale and /products/stylewalker have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    /collections/incal-aminte, /collections/shoes-winter, /collections/incaltaminte-barbati and /collections/incaltaminte-femei 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 63 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 12 small tap targets

    12 of 57 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 “TypeError: Cannot read properties of undefined (reading 'querySelector')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • No Referrer-Policy

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

  • No Permissions-Policy

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

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

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

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (1ashop.ro).

  • Valid certificate (87 days left)

    The certificate from Let's Encrypt · YE1 verifies for 1ashop.ro and is valid for another 87 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://1ashop.ro redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 43 links work

    All 43 links checked from your homepage (40 internal, 3 external) answered without errors.

Domain and trust

1 checks passed
  • Certificate issuers are restricted

    CAA records allow only pki.goog, letsencrypt.org, ssl.com and digicert.com to issue certificates for 1ashop.ro, so a mis-issued certificate from anyone else is refused.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

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

  • No analytics detected

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

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

  • About 1,013 words of copy

    The homepage carries about 1,013 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 2 short forms

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

  • Direct contact links

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

Email authentication

1 to fix70
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be 1ashop.ro is still delivered. Add a report address, check the reports, then move to quarantine.

  • Email authentication score: 70/100

    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.

2 checks passed
  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 ip4:212.44.113.31 ip4:146.247.26.120 ip4:146.247.26.123 a mx include:_spf.si-shell.net include:spf.squalomail.co…”.

  • DKIM signing found

    A DKIM key is published (selector “default” and “mandrill”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 16 cookies set on arrival

    16

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

  • 23 other companies contacted

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

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 35 issues on 1ashop.ro, including 15 speed issues, 5 SEO issues and 3 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