Your position
38th percentile of 37 sites audited. The average site scores 73, the median 73.
Website audit report
textguru.ru
69
/ 100
C · Needs work
1 critical and 11 high-severity issues found across 123 checks.
- Checks run
- 123
- Passed
- 77
- Failed
- 36
- Pages crawled
- 12
Scanned 2026-09-29T22:14:02+00:00 · 1 host IP · cert expires in 56 days
This report is not offered to search engines. It is reachable by link only. If you own textguru.ru you can publish or delete it.
How you compare
Measured against every site SEOking has audited: a corpus that grows with each scan and cannot be reconstructed after the fact.
Sites built like yours
66 is the average for the 6 sites we have audited on custom / origin / other-dns, and you are above it.
The most unusual thing you fail
Content is in the HTML, not built by JavaScript
100% of the sites we have audited get this right and yours does not. Of everything on this report, it is the fault that most sets you apart from your competition, which makes it the first thing worth fixing.
Inbox Trust Index
Our own measure of whether your domain is trusted by the systems that decide if mail reaches an inbox. No other website audit reports this. It is built from BounceZero's deliverability platform.
0
/ 100
Critical
Your domain fails the basic checks receivers run before they trust a message.
What is pulling it down: SPF record · DMARC enforcement · DKIM signing. See the email deliverability section below.
Measured against our corpus
We have measured deliverability across 255,979 domains. Yours is not among them, which simply means no one has needed to verify an address at it. The score above is from live measurements of your own DNS.
For context, 4.3% of the domains we have measured accept mail to any address, which makes their bounce behaviour unpredictable.
How your page actually renders
Loaded in a real browser at phone size. This is close to what a visitor and Google's renderer see.
- Largest paint
- 1.0s
- Layout shift
- 0
- Requests
- 6
- Words rendered
- 275
- JS errors
- 0
- Failed resources
- 1
Your plan
The 36 faults on this report come from 16 underlying causes. Fixing a cause fixes everything under it, so this is ordered by score returned per unit of work, not by severity alone.
The 6 quickest steps here take you from 69 to about 80. That is 11 points for changes measured in minutes and hours, not weeks.
1. Fix email authentication
DNS edit · minutes→ 75/100These are all records in your DNS. One editing session fixes every one of them, and it is the change most likely to stop your mail being filtered.
Fixes 4 findings: Exactly one SPF record · DMARC policy is enforced · DKIM signing is configured · BIMI logo published
2. Make the structured data qualify
Template change · a few hours→ 80/100Rich results — ratings, prices, FAQs, breadcrumbs — are what turn a listing into an advert, and they are decided by whether a few required properties are present. Markup that is invalid or incomplete is work already done that currently earns nothing.
Fixes 6 findings: The business is a describable entity · Content is marked up to be answered · The business is identified in structured data · Breadcrumbs are marked up · Site-wide search is declared · The entity links out to its profiles
3. Harden DNS and hosting
Server or CDN config · under an hour→ 83/100Resilience and reputation work — lower urgency, but cheap while you are already in these systems.
Fixes 4 findings: Domain can receive email · All page resources load successfully · DNSSEC enabled · CAA record restricts certificate issuance
4. Close the takeover and impersonation gaps
DNS edit · minutes→ 83/100A subdomain pointing at a service that released it can be claimed by anyone, who then publishes on your domain. Deleting the record costs nothing and closes it immediately.
Fixes 1 finding: No lookalike domain can send mail as your brand
5. Strengthen thin pages
Content work · days→ 87/100Pages with little unique content rarely rank and can hold back how the whole site is judged.
Fixes 3 findings: Content is in the HTML, not built by JavaScript · Navigation links are crawlable without JavaScript · Pages have enough content
6. Point the site's own authority at the pages that earn
Template change · a few hours→ 89/100Internal links decide which of your pages search engines treat as important, and the decision is usually an accident of navigation design. It costs nothing to change and it changes what ranks.
Fixes 3 findings: Every page is linked from somewhere · Every page is linked from another · Internal authority is spread, not pooled
7. Fix what search engines are allowed to see
Server or CDN config · under an hour→ 90/100These decide whether your pages can appear at all. Nothing else on this report matters until they are right.
Fixes 1 finding: Homepage canonical is correct
8. Show who stands behind the content
Content work · days→ 92/100Google's guidance asks who produced a page and why they should be trusted. For advice, health, legal or financial topics an anonymous, undated page competes badly against a named one.
Fixes 3 findings: Content identifies who wrote it · There is a route to who you are · A publisher is declared in structured data
9. Stop JavaScript overriding the indexing directives
Development work · days to weeks→ 94/100A canonical or noindex injected at runtime silently overrides what the server said, and the served HTML still looks correct to anyone reading the source.
Fixes 2 findings: Navigation does not depend on JavaScript · Content is readable without running JavaScript
10. Write the titles and descriptions
Content work · days→ 96/100Your title and description are the advert Google runs for you, free, every time someone searches.
Fixes 2 findings: Structured data present · Link previews are configured for X/Twitter
11. Fix the page on a phone
Template change · a few hours→ 97/100Google indexes the mobile version of your site, and these are measured in a real phone-sized browser rather than inferred. A page that scrolls sideways or needs pinching to read loses the visitor before the content matters.
Fixes 1 finding: Tap targets are big enough to hit
12. Reduce what the page has to load
Development work · days to weeks→ 98/100Image and script weight drive every speed metric you are failing. This is the slowest fix here and the one with the longest tail.
Fixes 2 findings: Images declare width and height · Images load lazily
13. Make the sitemap trustworthy
Server or CDN config · under an hour→ 99/100lastmod is how Google decides what to recrawl first. A timestamp that is identical on every URL is a build date, and Google learns to ignore lastmod for the whole site once it notices.
Fixes 1 finding: Sitemap lastmod dates are meaningful
14. Decide whether AI assistants may cite you
Server or CDN config · under an hour→ 99/100A growing share of questions are answered without a results page. Being quotable is a distribution channel, and it is usually blocked by a plugin default rather than a decision.
Fixes 1 finding: A curated summary is published for assistants
15. Remaining individual fixes
Mixed · varies→ 99/100These do not share a root cause with anything else on the report.
Fixes 1 finding: Navigation is present on every page
16. Serve images at the right size and format
Development work · days to weeks→ 100/100Images are what Largest Contentful Paint usually measures, and WebP is typically a third smaller than the same JPEG. On image-led pages this is the largest saving available.
Fixes 1 finding: Images are sized for the device
Fix these first
Ranked by severity, then by how much score each returns.
- critical
1. Exactly one SPF record
+14 ptsNo SPF record at all. Anyone on the internet can send email that appears to come from your domain, and your own mail is far more likely to be filtered.
How to fix: Publish an SPF record listing every service that sends your email.
- high
2. Content is in the HTML, not built by JavaScript
+10 ptsThe HTML your server sends contains 84 words; after JavaScript runs the page has 275. Almost none of your content exists until scripts execute. Google does render JavaScript, but it does so on a delay and not always completely, so this content is indexed late or partially — and other crawlers and preview tools never see it at all.
raw HTML: 84 words · rendered: 275 words · 3.3× more after JS
How to fix: Server-render or pre-render your main content so it is present in the initial HTML response.
- high
3. DMARC policy is enforced
+9 ptsNo DMARC record. You have neither protection against domain spoofing nor any visibility into it.
How to fix: Publish v=DMARC1; p=none; rua=mailto:dmarc@yourdomain to start, then tighten to quarantine.
- high
4. DKIM signing is configured
+8 ptsNo DKIM keys found on any common selector. Without DKIM your mail cannot prove it was not altered in transit, and DMARC cannot pass on forwarded messages.
How to fix: Enable DKIM in your mail provider and publish the key it gives you.
- high
5. No lookalike domain can send mail as your brand
+8 ptsWe generated and checked 60 plausible misspellings and variants of your domain. 3 of the 4 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.
testguru.ru [mail configured] textguru.com [mail configured] textguru.org [mail configured] text-guru.ru
How to fix: Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.
Full results
Security & trust
Whether the connection, certificate and headers hold up.
10 passed · 0 failed
100%
- ✓Served over HTTPS
Secure connection working.
- ✓HTTP redirects to HTTPS
Plain HTTP requests are redirected to the secure version.
- ✓No insecure mixed content
All resources load securely.
- ✓Certificate is not near expiry
Certificate valid for another 56 days (expires 2026-11-25).
- ✓Modern TLS version
Negotiated TLSv1.3.
- ✓HSTS header
HSTS is set.
- ✓Content Security Policy header
Content Security Policy is set.
- ✓MIME sniffing protection header
MIME sniffing protection is set.
- ✓Clickjacking protection header
Clickjacking protection is set.
- ✓Referrer policy header
Referrer policy is set.
Email deliverability
Whether your mail reaches inboxes or spam folders.
0 passed · 5 failed
0%
- ✕Exactly one SPF recordcritical
No SPF record at all. Anyone on the internet can send email that appears to come from your domain, and your own mail is far more likely to be filtered.
Publish an SPF record listing every service that sends your email.
- ✕DMARC policy is enforcedhigh
No DMARC record. You have neither protection against domain spoofing nor any visibility into it.
Publish v=DMARC1; p=none; rua=mailto:dmarc@yourdomain to start, then tighten to quarantine.
- ✕DKIM signing is configuredhigh
No DKIM keys found on any common selector. Without DKIM your mail cannot prove it was not altered in transit, and DMARC cannot pass on forwarded messages.
Enable DKIM in your mail provider and publish the key it gives you.
- ✕Domain can receive emailhigh
No MX records. This domain cannot receive email at all — messages to anyone @ this domain bounce.
Add MX records pointing at your mail provider.
- ✕BIMI logo publishedlow
No BIMI record. With DMARC at enforcement you could display your logo next to your messages in Gmail and Apple Mail.
Once DMARC is at quarantine or reject, publish a BIMI record with an SVG logo.
Speed & Core Web Vitals
How fast real visitors experience the site.
6 passed · 3 failed · 1 skipped
74%
- ✕Images declare width and heightmedium
0 of 1 images declare dimensions. Images without dimensions cause the page to jump as they load, which is what Cumulative Layout Shift measures.
Set width and height attributes on every image.
- ✕Images load lazilylow
0 of 1 images use lazy loading.
Add loading="lazy" to images below the fold.
- ✕Images are sized for the devicelow
0 of 12 image(s) provide a srcset. Without one, a phone downloads the full desktop image and then scales it down — paying for pixels it never shows.
Add srcset and sizes so each device downloads an appropriate image.
- –Core Web Vitals from real users
Not available: PageSpeed API returned 429. This usually means the site does not yet have enough Chrome traffic for Google to report field data. Lab measurements below still apply.
- ✓Compression enabled
Served with gzip compression.
- ✓Server responds quickly
Median response across 12 page(s) was 77 ms.
- ✓Homepage HTML is not oversized
Homepage HTML is 8 KB.
- ✓Reasonable number of scripts
2 external script file(s) on the homepage.
- ✓Browser caching is allowed
Pages may be cached by browsers and CDNs.
- ✓Images use a modern format
No raster images found on the crawled pages.
Search fundamentals
The tags, files and signals search engines read first.
22 passed · 11 failed · 3 skipped
74%
- ✕Content is readable without running JavaScripthigh
The served HTML carries 84 words against 275 after JavaScript runs. Search engines render pages eventually; assistant crawlers generally do not — they fetch the HTML and read what is there. A page whose content only appears after scripts run is close to empty to them, so it cannot be quoted or cited however good the content is.
served 84 words → rendered 275
Render the main content server-side. This is the same fix as the js_content finding and it pays twice.
- ✕The business is a describable entityhigh
No Organization or Person markup. An assistant that cannot name the entity behind the site will describe the business from fragments, or not at all, which is how a competitor becomes the answer.
Add Organization JSON-LD with name, url, logo and sameAs links, so the description an assistant gives of the business is the one you wrote.
- ✕Content is marked up to be answeredhigh
No FAQPage, HowTo or QAPage markup. When an assistant answers a question about this service, the page has nothing structured to be cited from, so the citation goes to whoever wrote the answer block.
Add FAQPage schema for the questions the page answers (the answer must appear as visible text, not only in the markup) and HowTo for process content.
- ✕The business is identified in structured datamedium
No Organization markup. This is what Google assembles a knowledge panel from — the box with your logo, name and links that appears beside branded searches — and what connects your site to your social profiles. Without it Google infers your identity from third parties instead of from you.
Add Organization JSON-LD with name, url, logo and sameAs links to your social profiles.
- ✕Homepage canonical is correctmedium
No canonical tag, so duplicate URLs of the same page can compete.
Set a self-referencing canonical on every page.
- ✕Structured data presentmedium
No structured data. Google is reading your page as plain text and cannot qualify you for any rich result.
Add JSON-LD for Organization and your primary content type.
- ✕Breadcrumbs are marked upmedium
No BreadcrumbList markup. Google replaces the raw URL in your listing with a readable breadcrumb trail when this is present, which is more legible and measurably more clickable — and it is one of the cheapest rich results to earn.
Add BreadcrumbList JSON-LD to every page below the homepage.
- ✕The entity links out to its profileslow
No entity markup to attach profiles to.
Add sameAs URLs to the Google Business Profile, LinkedIn, X and any other profiles the business owns.
- ✕Site-wide search is declaredlow
No WebSite markup. With a SearchAction it can give you a search box directly inside your Google listing for branded queries.
Add WebSite JSON-LD, with potentialAction/SearchAction if the site has its own search.
- ✕Link previews are configured for X/Twitterlow
No twitter:card tags. Open Graph covers most platforms, but X falls back to a bare link without them, and a link with no image or title is measurably less likely to be opened.
Add twitter:card ("summary_large_image"), twitter:title and twitter:description.
- ✕A curated summary is published for assistantslow
No /llms.txt. It is a short, plain-text map of what a site is and which pages matter — a convention some assistants read to decide what to quote, and cheap to publish. It is not yet a standard anyone is obliged to honour, so treat it as a low-cost bet rather than a requirement.
Publish /llms.txt: a heading, one paragraph describing the business, and a linked list of your most important pages.
- –International targeting
Not applicable — this site publishes in a single language and declares no regional or translated versions, so hreflang annotations are not needed. Adding them to a single-language site does nothing.
- –Search Console connected
Not measured — not configured on this instance. Connecting Search Console adds what no crawl can see: the queries this site already appears for, where it ranks, and how many people click. It is read-only and can be disconnected at any time.
- –Current search visibility
Not measured — ranking data is not configured on this instance.
- ✓Homepage is indexable
Homepage is open to indexing.
- ✓Mobile viewport declared
Mobile viewport is declared.
- ✓Homepage title is present and well sized
Title is 36 characters.
- ✓XML sitemap published
Sitemap found listing 21 URLs.
- ✓Homepage meta description is present
Description is 109 characters.
- ✓robots.txt does not block the site
robots.txt present and open to search engines.
- ✓Canonicals point at indexable pages
Every canonical points at a page that is allowed to be indexed.
- ✓Canonical targets are live pages
Canonical targets all return 200.
- ✓Sitemap and page directives agree
No page is both listed in the sitemap and marked noindex.
- ✓Structured data parses
All structured data blocks are valid JSON.
- ✓Noindex directives are readable
No page relies on a directive Google is blocked from reading.
- ✓Marked-up content qualifies for rich results
Every marked-up entity carries the properties Google requires.
- ✓Most crawled pages are indexable
12 of 12 crawled page(s) (100%) can actually be indexed.
- ✓No canonical chains
No canonical points at a page that then canonicals somewhere else.
- ✓Sitemap lists canonical pages only
Every sitemap URL is its own canonical.
- ✓AI assistants can cite this site
Every major assistant is allowed to read and cite these pages.
- ✓Pages are close to the homepage
Every crawled page sits within four levels of the homepage (deepest: 1).
- ✓Social preview configured
3 Open Graph tags found.
- ✓URLs are readable
URLs use lowercase, hyphenated, extension-free paths.
- ✓Content is not served behind query parameters
0 of 12 crawled URLs carry query parameters other than tracking tags.
- ✓Page language declared
Language attribute present.
- ✓Model-training access is stated
No model-training crawler is blocked, so this content may be used to train future models. This is a business decision rather than an SEO one, and it is separate from being cited in answers: refusing training does not remove you from AI results, and allowing it does not put you in them.
Content & structure
Whether pages are unique, linked and crawlable.
17 passed · 8 failed · 1 skipped
70%
- ✕Every page is linked from somewherehigh
10 of 12 crawled pages had no internal link pointing at them. Search engines discover pages by following links, so an unlinked page is found late or not at all — and passes on none of its authority.
10 affected URLs
Link these from a relevant parent page, your navigation, or a hub page.
- ✕Pages have enough contentmedium
12 of 12 crawled pages carry under 150 words. Thin pages rarely rank and can drag down how the whole site is assessed.
10 affected URLs
Expand or consolidate thin pages so each answers a real question.
- ✕Content identifies who wrote itmedium
No author is named anywhere — no byline, no author metadata and no author in your structured data. Google's guidance on helpful content asks who produced it and why anyone should trust them, and for advice, health, legal or financial pages an anonymous page competes badly against one with a named, credentialed author.
Add a byline with a real name linking to an author page, and an author property in your Article or Organization markup.
- ✕Every page is linked from anothermedium
10 crawled page(s) are not linked from any other page we fetched. A page reachable only from a sitemap receives no internal authority at all, and is crawled rarely — it can rank, but it starts from nothing and stays there.
textguru.ru/ocr textguru.ru/headline textguru.ru/commas textguru.ru/improve textguru.ru/poem textguru.ru/equation
10 affected URLs
Link them from a relevant hub page or from navigation, using the subject as the link text.
- ✕There is a route to who you aremedium
No link to an about, team or contact page was found in the pages crawled. These are the pages both people and search engines use to decide whether a site belongs to a real business, and their absence is one of the strongest signals of a site that is not worth trusting.
Link an About and a Contact page from your main navigation or footer.
- ✕Navigation is present on every pagemedium
At least one page carries fewer than three internal links, which usually means the navigation failed to render there.
Make sure header and footer navigation render server-side on every template, including error and landing pages.
- ✕Internal authority is spread, not pooledlow
One page receives more than half of all internal links found. That concentrates authority in one place while the rest of the site is starved of it.
Link deliberately to the pages you want to rank, not only to the same one from every template.
- ✕A publisher is declared in structured datalow
No publisher in your structured data. It ties each page back to the organisation that stands behind it, which is what carries trust from your brand to an individual article.
Add a publisher property naming your Organization, with its logo.
- –Content carries recent dates
Not measured — no page declares a publication or modification date, so how recently the site was maintained cannot be determined. That is normal for a brochure site and worth fixing for anything article-based.
- ✓Page titles are unique
All 12 crawled pages have distinct titles.
- ✓Every page has a meta description
0 of 12 crawled pages have no meta description.
- ✓Images have alt text
0 of 12 images across the crawl have no alt attribute. Alt text is how search engines read images and how screen readers describe them.
- ✓Pages are meaningfully different from each other
No two crawled pages share substantially the same text.
- ✓No broken internal pages
All 12 crawled pages returned successfully.
- ✓Missing pages return a real 404
No page answers 200 while telling the visitor nothing was found.
- ✓Navigation promotes pages that earn money
2 link(s) appear on nearly every page — the site-wide navigation, which is where most internal authority is allocated.
- ✓Each page covers a distinct subject
No two crawled pages appear to target the same subject.
- ✓Pages deliver what their titles promise
Every page's body covers the subject its title and heading announce.
- ✓Meta descriptions are unique
All 12 descriptions found are distinct.
- ✓Links describe where they go
0 of 59 internal link(s) use text like 'click here' or no text at all.
- ✓No phrase is repeated unnaturally
No phrase dominates a page's text.
- ✓One H1 per page
0 of 12 pages do not have exactly one H1 heading.
- ✓No long redirect chains
No multi-step redirects found.
- ✓Sitemap matches the real site
Sitemap lists 21 URLs; we reached 12 by crawling. 10 sitemap URLs were not linked from the pages we visited.
- ✓No dead-end pages
Every crawled page links onward.
- ✓Where internal authority goes
Internal links concentrate authority on the pages below, in order. This is the site's own ranking of itself, derived from how it links — read it against what the business actually sells, because search engines read it the same way. Only the crawled sample is modelled, so this describes the navigation rather than every page.
Local business signals
What Google needs to place you in map results.
0 passed · 0 failed · 1 skipped
100%
- –Local business signals
Not applicable — nothing on this site indicates a physical location customers visit: no address, phone link, opening hours, map or local business markup. Local search checks are skipped and do not affect the score. If you do serve customers from premises, publishing an address and phone number is the place to start.
Infrastructure
DNS, hosting and delivery configuration.
13 passed · 4 failed · 3 skipped
79%
- ✕No lookalike domain can send mail as your brandhigh
We generated and checked 60 plausible misspellings and variants of your domain. 3 of the 4 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.
testguru.ru [mail configured] textguru.com [mail configured] textguru.org [mail configured] text-guru.ru
Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.
- ✕Sitemap lastmod dates are meaningfulmedium
Only 0 of 21 sitemap URL(s) declare a lastmod. It is the signal Google uses to decide what to recrawl first, so without it updates are found late.
[]
Emit lastmod from the date the page content actually changed, not from the time the sitemap was generated.
- ✕DNSSEC enabledlow
DNSSEC is not enabled, so DNS answers for your domain can't be cryptographically verified.
Enable DNSSEC at your DNS provider.
- ✕CAA record restricts certificate issuancelow
No CAA record, so any certificate authority may issue certificates for your domain.
Publish a CAA record naming the certificate authority you use.
- –Web server IP is not blacklisted
Not checked: the blocklists declined queries from this resolver, so reputation could not be confirmed either way. This is excluded from your score rather than guessed at.
- –Server log analysis
Not measured — no log file supplied. Server logs are the only source that shows what Googlebot actually fetched rather than what it could fetch: which pages it spends its crawl on, which it has never asked for, and what it receives when it does.
- –Whole-site analysis
Not measured — no whole-site crawl has been run for this domain. The audit above reasons from a sample of pages chosen to cover each template, which describes how the site is built. It cannot say how many of the site's pages are indexable, which templates are thin across every instance, or what sits too deep to be crawled — those are counts, and a sample cannot produce one.
- ✓Redundant nameservers
2 nameserver(s) configured.
- ✓No subdomain can be taken over
Checked 5 subdomain(s); none point at a cloud service that has released them.
- ✓No staging or development sites are publicly indexable
Certificate transparency lists 5 hostname(s) for this domain and none of the development-style hosts are both live and open to indexing.
- ✓No unbounded URL spaces
No filter, session or calendar URLs that would generate an unbounded space were found.
- ✓Pages are reached without redirect chains
Every page was reached directly or in a single hop.
- ✓Crawled URLs return content
0 of 12 URL(s) followed during this crawl returned a redirect or an error (0%).
- ✓Certificate is not shared with unrelated domains
Your certificate covers only your own domain.
- ✓Sitemap files are within Google's limits
Every sitemap file is within the 50,000 URL and 50 MB limits.
- ✓Internal links pass authority
0 internal link(s) are marked nofollow.
- ✓Software versions are not disclosed
No version numbers advertised in response headers.
- ✓Certificate surface is proportionate
5 hostname(s) appear in this domain's public certificate history, issued by Let's Encrypt, GlobalSign nv-sa.
- ✓Hosting network identified
Served from AS29182 (RU-JSCIOT JSC IOT), announced in 188.120.224.0/20 — a block of 4,096 addresses.
- ✓What this audit examined
12 page(s) were examined, chosen to cover 11 of the 21 distinct page templates found across 21 known URLs. Pages are sampled by template rather than in sitemap order, because the first pages of a sitemap are usually all the same kind — a sample of one template would describe that template rather than the site. Findings below therefore apply to the templates listed, and a fault in a template is normally a fault on every page built from it.
Off-page authority
Who links to this site, with what text, and how that compares.
0 passed · 0 failed · 1 skipped
100%
- –Off-page profile
Not measured — off-page data is not configured on this instance.
What Google's renderer sees
The site loaded in a real browser, the way a visitor and a crawler get it.
9 passed · 5 failed
63%
- ✕Content is in the HTML, not built by JavaScripthigh
The HTML your server sends contains 84 words; after JavaScript runs the page has 275. Almost none of your content exists until scripts execute. Google does render JavaScript, but it does so on a delay and not always completely, so this content is indexed late or partially — and other crawlers and preview tools never see it at all.
raw HTML: 84 words · rendered: 275 words · 3.3× more after JS
Server-render or pre-render your main content so it is present in the initial HTML response.
- ✕Navigation links are crawlable without JavaScripthigh
Only 4 links exist in the served HTML but 30 appear after JavaScript. Crawlers discover pages by following links — if your navigation is built by script, much of your site may never be found.
Render navigation as real <a href> elements in the initial HTML.
- ✕Navigation does not depend on JavaScripthigh
The served HTML exposes 4 internal links and the rendered page 30. Most of this site's navigation only exists after JavaScript runs, so pages reachable only through it are discovered late or not at all, and the link equity those links should pass is deferred with them.
served 4 → rendered 30 internal links
Emit real <a href> links in the server response for anything that should be crawled and ranked.
- ✕All page resources load successfullymedium
1 resource(s) failed to load. Missing images and stylesheets are visible to customers; missing scripts break features.
https://mc.yandex.ru/metrika/tag.js?id=112189643 (failed)
1 affected URL
Fix or remove these URLs.
- ✕Tap targets are big enough to hitmedium
15 of 35 tappable element(s) are smaller than 48x48 pixels. On a phone that means links and buttons that are hard to hit without zooming, and mis-taps on a checkout or contact button cost conversions directly.
✦ ТекстГуру (127x30) Генератор текста (125x24) Орфография (94x24) Запятые (60x24) Перефразировать (131x24)
Give tappable elements at least 48x48 CSS pixels and 8 pixels of spacing — usually padding on the link rather than a bigger font.
- ✓The mobile page matches the desktop page
What the server sends a phone matches what it sends a desktop browser.
- ✓JavaScript does not rewrite indexing directives
The canonical and robots directives are the same before and after JavaScript runs.
- ✓Largest Contentful Paint under 2.5s (lab)
Measured 1.0s on a simulated phone viewport. Google's threshold for 'good' is 2.5s.
- ✓Layout stays stable while loading (lab)
Cumulative Layout Shift measured at 0.000 (good is 0.1 or less).
- ✓No JavaScript errors on load
The page loaded without JavaScript errors.
- ✓The page fits the screen
The page fits the mobile viewport with no sideways scrolling.
- ✓No excessive JavaScript blocking
0 long JavaScript task(s) blocked the main thread while loading.
- ✓Body text is legible on a phone
0 of 44 text block(s) render below 12px on a mobile viewport.
- ✓Reasonable number of requests
The page made 6 network requests to load.
Scan details
| Final URL | https://textguru.ru/ |
|---|---|
| Host IPs | 188.120.238.193 |
| Pages crawled | 12 of 12 attempted |
| Sitemap URLs | 21 |
| Nameservers | ns1.parken.ru, ns2.parken.ru |
| Mail servers | none |
| DKIM selectors | none found |
| TLS | TLSv1.3 · TLS_AES_128_GCM_SHA256 · issued by Let's Encrypt |
| Detected stack | custom / origin / other-dns |
| Browser render | Camoufox (stealth Firefox) · 5.0s · 275 words, 30 links after JavaScript |
12 URLs crawled
- https://textguru.ru/
- https://textguru.ru/headline
- https://textguru.ru/commas
- https://textguru.ru/equation
- https://textguru.ru/greeting
- https://textguru.ru/history
- https://textguru.ru/improve
- https://textguru.ru/letter
- https://textguru.ru/mainidea
- https://textguru.ru/ocr
- https://textguru.ru/password
- https://textguru.ru/poem
Want these fixed?
BounceZero Ltd does this work: technical remediation, local SEO and email deliverability. Tell us what you want fixed and we'll reply with what it takes. No call required, no obligation.
Watch this site
We re-audit on a schedule and email you only when a check that was passing starts failing. That is usually a recent change to the site or its DNS, and it is findable while still fresh. No digest, no newsletter.
Monitoring means repeatedly fetching your site and emailing about it, so we ask you to prove you own textguru.ru first.