Website review, no card needed

yoosell.net logo

yoosell.net website review

Visit site (opens in a new tab)Reviewed 10 November 202639 issues · 81 checks

This review found 39 issues worth fixing on yoosell.net, 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

Full-page screenshot of yoosell.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. yoosell.net at 0.6 s0.6 s
  2. yoosell.net at 1.1 s1.1 s
  3. yoosell.net at 1.7 s1.7 s
  4. yoosell.net at 2.3 s2.3 s
  5. yoosell.net at 2.8 s2.8 s
  6. yoosell.net at 3.4 s3.4 s
  7. yoosell.net at 4.0 s4.0 s
  8. yoosell.net at 4.5 s4.5 s

Speed

9 to fix54
  • Render-blocking requests

    2.9 s

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

  • Reduce unused JavaScript

    600 ms · 561 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.6 MB and 845 ms of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • Google CDN adds 505 ms

    505 ms

    Google CDN costs a phone 505 ms of main-thread work and 743 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

    400 ms · 158 KiB

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

  • Reduce unused CSS

    300 ms · 163 KiB

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

  • Main-thread work: 3.8 s

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

  • zohopublic.com adds 6 ms

    6 ms

    zohopublic.com costs a phone 6 ms of main-thread work and 497 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 · 41 KiB

    41 KiB could be saved by minifying JavaScript.

  • 13 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Improve image delivery

    34 KiB

    3 images could be 34 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 177 ms

    177 ms

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

Core Web Vitals

6 to fix56
  • Largest Contentful Paint: 7.3 s

    7.3 s

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

  • Time to Interactive: 16.1 s

    16.1 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Total Blocking Time: 442 ms

    442 ms

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

  • 1 image without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix85
  • Page weight: 2.9 MB in 112 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 112 requests on a phone: scripts 1.3 MB (46), images 664 KiB (13) and fonts 383 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.83 g

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

7 to fixGoogle 9493
  • 27 text elements with low contrast

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

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

    All page content should be contained by landmarks: 32 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 7 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 H1 headline

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

  • Title is short (24 characters)

    Your title is only 24 characters: “Home – Español | Yoosell”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (39 characters)

    Your meta description is only 39 characters: “¡Aumenta el potencial de tu negocio con”. 70 to 160 characters is enough to sell the click.

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

  • 15 internal links, 4 external

    The homepage links to 15 pages on yoosell.net and 4 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.yoosell.net/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • 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.yoosell.net/sitemap_index.xml.

AI search readiness

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

    Your Organization JSON-LD is missing url, logo, 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.yoosell.net/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 (685 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix71
  • 1 page points its canonical at the homepage

    https://www.yoosell.net/en declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    https://www.yoosell.net/politica-de-privacidad and https://www.yoosell.net/es/politica-de-privacidad all use the title “Política de privacidad | Yoosell”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.yoosell.net/en has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.yoosell.net/politica-de-privacidad and https://www.yoosell.net/es/politica-de-privacidad use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://www.yoosell.net/en, https://www.yoosell.net/es/blog/esquema-nacional-seguridad-ens-lastpass, https://www.yoosell.net/es/blog/esquema-nacional-de-seguridad-ens and https://www.yoosell.net/es/blog/guia-de-ciberamenazas-ingenieria-social have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.yoosell.net/politica-de-privacidad, https://www.yoosell.net/es/blog/esquema-nacional-seguridad-ens-lastpass and https://www.yoosell.net/es/blog/guia-de-ciberamenazas-ingenieria-social took over 3 s to send their HTML from our server.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 3 small tap targets

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

  • 2 low-resolution images

    2 images are 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

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 821 words of copy

    The homepage carries about 821 words of visible text.

2 checks passed
  • 2 short forms

    2 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and LinkedIn Insight.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 3 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.

  • 15 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
WHG Hosting Services Ltd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on yoosell.net, 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