Website review, no card needed

toolweb.online logo

toolweb.online website review

Visit site (opens in a new tab)Reviewed 10 November 202613 issues · 47 checks

This review found 13 issues worth fixing on toolweb.online, 3 of them high impact, across 47 checks. The most urgent: no call to action on the first screen. 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 toolweb.online (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. toolweb.online at 0.4 s0.4 s
  2. toolweb.online at 0.8 s0.8 s
  3. toolweb.online at 1.1 s1.1 s
  4. toolweb.online at 1.5 s1.5 s
  5. toolweb.online at 1.9 s1.9 s
  6. toolweb.online at 2.3 s2.3 s
  7. toolweb.online at 2.6 s2.6 s
  8. toolweb.online at 3.0 s3.0 s

Speed

99
  • Render-blocking requests

    250 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Yandex Metrica), adding 73 KiB and 54 ms of main-thread time.

  • Use efficient cache lifetimes

    57 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    38 KiB

    About 38 KiB of JavaScript is downloaded but never used on this page.

  • 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
  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.2 s

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

Core Web Vitals

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

6 checks passed
  • Cumulative Layout Shift: 0.069

    0.069

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

  • Time to Interactive: 2.0 s

    2.0 s

    The page is fully interactive after 2.0 s.

  • First Contentful Paint: 0.8 s

    0.8 s

    The first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.9 s

    0.9 s

    Your largest element renders in 0.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Создание надёжных случайных паролей с настройкой длины и си…”.

  • Speed Index: 1.8 s

    1.8 s

    Visually, the page fills in at 1.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 1 ms

    1 ms

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

Images and page weight

100
  • About 0.03 g of CO₂ per visit

    0.03 g

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

1 checks passed
  • Page weight: 98 KiB in 17 requests

    98 KiB

    Your homepage downloads 98 KiB in 17 requests on a phone: scripts 82 KiB (4), other files 8 KiB (8) and stylesheets 3 KiB (1). That is a lean page.

Accessibility

1 to fixGoogle 10098
  • 1 form field without a label

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

1 checks passed
  • 32 automated accessibility rules passed

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

SEO

4 to fixGoogle 10087
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

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

5 checks passed
  • Meta description: 115 characters

    Your meta description is 115 characters: “Бесплатные онлайн-инструменты: конвертеры единиц, генераторы, форматирование JSON, Base64, QR-коды и многое другое.”.

  • One H1 headline

    Your main headline reads: “Онлайн утилиты”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Онлайн инструменты и конвертеры — бесплатно и без регистрации”.

  • 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://toolweb.online/sitemap.xml.

AI search readiness

1 to fix83
  • 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://toolweb.online/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.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25
  • 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.

  • No analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 113 words

    The homepage has only about 113 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 7 cookies set on arrival

    7

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

  • 2 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
NovoServe B.V.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 13 issues on toolweb.online, including 4 SEO issues and 6 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