severnaya-zvezda.tech
Северная Звезда — заказная разработка ПО
0 failed · 5 warnings · 24 passed
Audited Sun, 26 Jul 2026 11:15:36 GMT · https://severnaya-zvezda.tech/
Meta & Head
22.9/25
Title, description, canonical, social tags — what search engines read first.
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.
Twitter card taglow impactlow effort
No twitter:card meta tag found
X (Twitter) layers its own card markup on top of Open Graph, and without a twitter:card tag your shared links may render as plain text instead of a large image preview. Add <meta name="twitter:card" content="summary_large_image"> alongside your Open Graph tags; X will fill in the title, description, and picture from og:title, og:description, and og:image. Keep og:image an absolute URL — a relative or missing image is the usual reason cards show up without a picture.
7 passing checks
- Title tag<title> is "Северная Звезда — заказная разработка ПО" (40 characters)
- Meta descriptionMeta description is "Заказная разработка высоконагруженных систем, решений для цепочек поставок и промышленного IoT на Java, Kotlin и .NET." (118 characters)
- Canonical URLCanonical href is "https://severnaya-zvezda.tech/"
- Viewport meta tagViewport is "width=device-width, initial-scale=1"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Page allows indexingNo restrictive robots meta tag
Content & Structure
20.8/25
Headings, copy depth, images, structured data, internal linking.
Word counthigh impactlow effort
311 words of visible text
With only a few hundred words, this page gives search engines little to index and often loses to more thorough competitors targeting the same query. Expand it toward 600+ words of genuinely useful material: answer the questions visitors arrive with, and add examples, specifics, an FAQ section, or step-by-step detail. Don't pad with fluff or repeat keywords to hit a number — length should be a byproduct of covering the topic properly, never the goal itself.
Structured data (JSON-LD)medium impactmedium effort
No JSON-LD structured data blocks found
Structured data makes your listing eligible for rich results — star ratings, FAQs, breadcrumbs, product prices — which occupy more space on the results page and draw more clicks than plain blue links. Add a <script type="application/ld+json"> block with a schema.org type that matches the page: Organization or WebSite for a homepage, Article for posts, Product for product pages. Only mark up content actually visible on the page — markup for invisible content violates Google's guidelines and can earn a manual action.
6 passing checks
- Single H1 heading1 h1 found: "Высоконагруженные системы,которые держат нагрузку."
- Heading hierarchy11 headings in order without skipped levels
- Hreflang annotations3 valid hreflang link(s) including x-default
- HTML lang attribute<html lang="ru">
- JavaScript-dependent contentvisible text ~3632 chars in the initial HTML
- Internal linking14 internal, 0 external links
Technical
24.4/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
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.
11 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- Short redirect chainno redirects; URL resolves directly
- robots.txt present and permissiverobots.txt exists and allows crawling
- XML sitemap availablesitemap.xml exists and is valid XML
- Fast time to first byte398 ms
- Reasonable HTML size10.9 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.