2shemi.com
2 Схемы | Принципиальные электросхемы, калькуляторы для авто, подключение и распиновка разъёмов
2 failed · 5 warnings · 22 passed
Audited Sat, 18 Jul 2026 04:00:20 GMT · https://2shemi.com/
Meta & Head
21.5/25
Title, description, canonical, social tags — what search engines read first.
Title taghigh impactlow effort
<title> is "2 Схемы | Принципиальные электросхемы, калькуляторы для авто, подключение и распиновка разъёмов" (95 characters)
Search engines truncate titles past roughly 60 characters and often rewrite very short or vague ones, so the message you wrote may never actually be shown. Rewrite the title to 30–60 characters that lead with the primary keyword and end with your brand, e.g. "Merge PDF Files Online Free | YourBrand". Front-load the important words, since truncation always cuts from the end. Don't pad a short title with repeated keywords just to hit the range — clarity wins clicks, not length.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:image
Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:image tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.
7 passing checks
- Meta descriptionMeta description is "Принципиальные электросхемы, калькуляторы для авто, подключение и распиновка разъёмов" (85 characters)
- Canonical URLCanonical href is "https://2shemi.com/"
- Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingrobots: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Content & Structure
17.2/25
Headings, copy depth, images, structured data, internal linking.
Single H1 headinghigh impactlow effort
0 h1 headings found
The h1 is the visible headline of the page and one of the clearest signals to search engines of what it's about; with none present, engines lean on surrounding text and may misread the topic. Add exactly one h1 near the top that states the main topic in plain language and includes the primary keyword, e.g. <h1>Merge PDF Files Online</h1>. Don't fake it with a styled <div> — the semantic tag itself is what crawlers and screen readers actually read.
Image alt textmedium impactlow effort
26 of 56 images have alt text
Alt text is how search engines understand what an image shows — it feeds image-search rankings and is what screen readers announce to blind visitors. Add a short, specific alt attribute to every meaningful image, describing the content rather than listing keywords: alt="Golden retriever puppy playing in snow" beats alt="dog puppy pet animal". Give purely decorative images an empty alt="" instead of omitting the attribute, so assistive technology knows to skip them rather than reading out the filename.
6 passing checks
- Heading hierarchy20 headings in order without skipped levels
- Word count5944 words of visible text
- Structured data (JSON-LD)JSON-LD types found: CollectionPage, BreadcrumbList, WebSite
- HTML lang attribute<html lang="ru-RU">
- JavaScript-dependent contentvisible text ~52390 chars in the initial HTML
- Internal linking170 internal, 0 external links
Technical
22.2/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
No mixed contentmedium impactlow effort
1 http:// subresource reference
Some images, scripts, or styles load over insecure http:// on this HTTPS page; browsers block insecure scripts outright and flag the page, which breaks functionality and undermines the padlock users look for. Update each reference to https:// — most hosts serve the same asset on both schemes — or re-host assets whose origins don't support TLS. Adding <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests"> is a quick safety net, but fix the underlying URLs too: hard-coded http:// links in databases and old content are the usual source.
XML sitemap availablemedium impactlow effort
no sitemap.xml found
Without an XML sitemap, search engines discover pages only by following links, so new, deep, or weakly linked pages get found slowly or not at all. Generate one at /sitemap.xml — most frameworks and CMSs have a generator built in or as a plugin — listing every canonical, indexable URL, then add "Sitemap: https://www.example.com/sitemap.xml" to robots.txt and submit it in Google Search Console. Keep it clean: listing redirected, noindexed, or 404 URLs erodes crawler trust in the whole file.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
9 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- Short redirect chainno redirects; URL resolves directly
- robots.txt present and permissiverobots.txt exists and allows crawling
- Fast time to first byte355 ms
- Reasonable HTML size281.4 KB
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.