Website review, no card needed
publisol.ro website review
Visit site (opens in a new tab)Reviewed 23 October 202636 issues · 83 checks
This review found 36 issues worth fixing on publisol.ro, 16 of them high impact, across 83 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73C- #82,074 of 110,322 reviewed websitesbeats 22%
- #51,459 of 62,689 online storesbeats 15%
- #48,249 of 57,205 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 295 ms |
| May 9, 2026 | 296 ms |
| May 16, 2026 | 295 ms |
| May 23, 2026 | 294 ms |
| May 30, 2026 | 305 ms |
| Jun 6, 2026 | 311 ms |
| Jun 13, 2026 | 319 ms |
| Jun 20, 2026 | 324 ms |
| Jun 27, 2026 | 328 ms |
| Jul 4, 2026 | 330 ms |
| Jul 11, 2026 | 330 ms |
| Jul 18, 2026 | 330 ms |
| Jul 25, 2026 | 326 ms |
| Aug 1, 2026 | 321 ms |
| Aug 8, 2026 | 327 ms |
| Aug 15, 2026 | 327 ms |
| Aug 22, 2026 | 337 ms |
| Aug 29, 2026 | 345 ms |
| Sep 5, 2026 | 333 ms |
| Sep 12, 2026 | 336 ms |
| Sep 19, 2026 | 334 ms |
| Sep 26, 2026 | 320 ms |
| Oct 3, 2026 | 327 ms |
| Oct 10, 2026 | 325 ms |
| Oct 17, 2026 | 322 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
Speed
Render-blocking requests
1.6 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 34
34/100Your mobile performance score is 34 (desktop: 63). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,545 HTML elements
The page has 4,545 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.1 s
A phone's processor spends 4.1 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and cdn-cookieyes.com and others), adding 899 KiB and 1.1 s of main-thread time.
Improve image delivery
800 ms · 124 KiB9 images could be 124 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
Reduce unused JavaScript
150 ms · 433 KiBAbout 433 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Google Tag Manager adds 385 ms
385 msGoogle Tag Manager costs a phone 385 ms of main-thread work and 314 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.
Facebook adds 259 ms
259 msFacebook costs a phone 259 ms of main-thread work and 231 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
251 KiB12 files are served with short cache lifetimes, so returning visitors download them again (251 KiB).
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 236 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 63 but mobile only 34. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 65 ms
65 msYour server sent the HTML in 65 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Cumulative Layout Shift: 0.66
0.66The layout shifts by 0.66 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 13.7 s
13.7 sThe page becomes fully interactive after 13.7 s. Good is under 3.8 s.
Largest Contentful Paint: 6.1 s
6.1 sYour largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a squared image depicting a fantasy toys and games universe…”.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user INP: 332 ms
332 msReal visitors wait 332 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 451 ms
451 msScripts block taps and scrolling for 451 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 295 ms to 322 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 438 ms
438 msReal visitors wait 438 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 2.4 MB in 201 requests
2.4 MBYour homepage downloads 2.4 MB in 201 requests on a phone: scripts 1.1 MB (56), other files 682 KiB (73) and images 402 KiB (32). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 83.1 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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
<svg> elements with an img or image role must have alternative text (1 element)
<svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 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.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Publisol.ro - Librărie online cu o colecție vastă de cărți și reviste”.
Meta description is long (278 characters)
Your meta description is 278 characters; Google truncates after about 160, so the end of your pitch is cut.
407 internal links, 21 external
The homepage links to 407 pages on publisol.ro and 21 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Librăria online Publisol”.
Canonical URL set
The canonical URL is https://publisol.ro/.
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://publisol.ro/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (2,339 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://publisol.ro/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://publisol.ro/collections/reduceri-jucarii has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.
6 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.
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 12 pages that loaded have a <title>.
Best practices
35 small tap targets
35 of 84 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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,147 words of copy
The homepage carries about 1,147 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
8 short forms
8 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
27 other companies contacted
Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 publisol.ro, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on publisol.ro, including 18 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.