SEOking

Website audit report

elektrik-24.com

73
/ 100
C · Needs work

1 critical and 5 high-severity issues found across 125 checks.

Checks run
125
Passed
77
Failed
37
Pages crawled
10

Scanned 2026-09-29T22:58:34+00:00 · 1 host IP · cert expires in 35 days

This report is not offered to search engines. It is reachable by link only. If you own elektrik-24.com 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.

Your position

49th percentile of 39 sites audited. The average site scores 73, the median 73.

Sites built like yours

67 is the average for the 8 sites we have audited on custom / origin / other-dns, and you are above it.

The most unusual thing you fail

The page fits the screen

90% 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.

12
/ 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.

Screenshot of elektrik-24.com on a mobile viewport
390 × 844 viewport
Largest paint
1.4s
Layout shift
0
Requests
106
Words rendered
2940
JS errors
0
Failed resources
3

Your plan

The 37 faults on this report come from 13 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 73 to about 84. That is 11 points for changes measured in minutes and hours, not weeks.

  1. 1. Fix email authentication

    DNS edit · minutes→ 79/100

    These 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 6 findings: Exactly one SPF record · DMARC policy is enforced · DKIM signing is configured · MTA-STS policy published · TLS reporting enabled · BIMI logo published

  2. 2. Make the structured data qualify

    Template change · a few hours→ 84/100

    Rich 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. 3. Complete the security headers

    Server or CDN config · under an hour→ 87/100

    All set in the same place — your web server or CDN. Half of them are single lines.

    Fixes 5 findings: HSTS header · Content Security Policy header · Cookies are protected · MIME sniffing protection header · Referrer policy header

  4. 4. Write the titles and descriptions

    Content work · days→ 90/100

    Your title and description are the advert Google runs for you, free, every time someone searches.

    Fixes 3 findings: Homepage title is present and well sized · Structured data present · Link previews are configured for X/Twitter

  5. 5. Harden DNS and hosting

    Server or CDN config · under an hour→ 91/100

    Resilience and reputation work — lower urgency, but cheap while you are already in these systems.

    Fixes 3 findings: All page resources load successfully · DNSSEC enabled · CAA record restricts certificate issuance

  6. 6. Fix the page on a phone

    Template change · a few hours→ 93/100

    Google 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 2 findings: Tap targets are big enough to hit · The page fits the screen

  7. 7. Reduce what the page has to load

    Development work · days to weeks→ 95/100

    Image and script weight drive every speed metric you are failing. This is the slowest fix here and the one with the longest tail.

    Fixes 4 findings: Reasonable number of scripts · Images declare width and height · Images load lazily · Reasonable number of requests

  8. 8. Show who stands behind the content

    Content work · days→ 97/100

    Google'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. 9. Close the takeover and impersonation gaps

    DNS edit · minutes→ 98/100

    A 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: Lookalike domains are not registered

  10. 10. Stop JavaScript overriding the indexing directives

    Development work · days to weeks→ 99/100

    A 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 1 finding: Navigation does not depend on JavaScript

  11. 11. Decide whether AI assistants may cite you

    Server or CDN config · under an hour→ 99/100

    A 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

  12. 12. Fix what search engines are allowed to see

    Server or CDN config · under an hour→ 99/100

    These decide whether your pages can appear at all. Nothing else on this report matters until they are right.

    Fixes 1 finding: Page language declared

  13. 13. Serve images at the right size and format

    Development work · days to weeks→ 100/100

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

  1. critical

    1. Exactly one SPF record

    +14 pts

    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.

    How to fix: Publish an SPF record listing every service that sends your email.

  2. high

    2. DMARC policy is enforced

    +9 pts

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

  3. high

    3. DKIM signing is configured

    +8 pts

    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.

    How to fix: Enable DKIM in your mail provider and publish the key it gives you.

  4. high

    4. Navigation does not depend on JavaScript

    +6 pts

    The served HTML exposes 20 internal links and the rendered page 44. 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 20 → rendered 44 internal links

    How to fix: Emit real <a href> links in the server response for anything that should be crawled and ranked.

  5. high

    5. The business is a describable entity

    +6 pts

    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.

    How to fix: 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.

Full results

Security & trust

Whether the connection, certificate and headers hold up.

6 passed · 5 failed
74%
  • ✕
    HSTS headermedium

    Missing. Tells browsers to only ever connect over HTTPS.

    Send Strict-Transport-Security: max-age=31536000; includeSubDomains

  • ✕
    Content Security Policy headermedium

    Missing. Limits where scripts may load from, which is the main defence against injected code and card skimmers.

    Add a Content-Security-Policy header, starting in report-only mode.

  • ✕
    Cookies are protectedmedium

    Cookies are set without the Secure and/or HttpOnly flags, so they can be read by scripts or sent over insecure connections.

    __ddg8_=CNtZaUlCpzn9pPaQ; Domain=.elektrik-24.com; Path=/; Expires=Tue, 29-Sep-2026 23:18:24 GMT, __ddg10_=1790722704; Domain=.elektrik-24.com; Path=/; Expires=Tue, 29-Sep-2026 23:18:24 GMT, __ddg9_=1

    Add Secure, HttpOnly and SameSite to every cookie you set.

  • ✕
    MIME sniffing protection headerlow

    Missing. Stops browsers guessing file types.

    Send X-Content-Type-Options: nosniff

  • ✕
    Referrer policy headerlow

    Missing. Controls how much of your URL is leaked to other sites.

    Send Referrer-Policy: strict-origin-when-cross-origin

  • ✓
    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 35 days (expires 2026-11-04).

  • ✓
    Modern TLS version

    Negotiated TLSv1.3.

  • ✓
    Clickjacking protection header

    Clickjacking protection is set.

Email deliverability

Whether your mail reaches inboxes or spam folders.

1 passed · 6 failed
12%
  • ✕
    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.

  • ✕
    MTA-STS policy publishedlow

    No MTA-STS policy, so mail to you can be delivered unencrypted if an attacker strips TLS.

    Publish an MTA-STS policy and the _mta-sts TXT record.

  • ✕
    TLS reporting enabledlow

    No TLS-RPT record, so delivery-encryption failures go unreported.

    Publish a _smtp._tls TXT record with a reporting address.

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

  • ✓
    Domain can receive email

    2 mail server(s) configured.

Speed & Core Web Vitals

How fast real visitors experience the site.

5 passed · 4 failed · 1 skipped
66%
  • ✕
    Images declare width and heightmedium

    0 of 24 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.

  • ✕
    Reasonable number of scriptsmedium

    18 external script file(s) on the homepage. Each one is a separate request that can block rendering.

    Remove unused third-party tags and combine what remains.

  • ✕
    Images load lazilylow

    0 of 24 images use lazy loading.

    Add loading="lazy" to images below the fold.

  • ✕
    Images are sized for the devicelow

    1 of 285 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 10 page(s) was 290 ms.

  • ✓
    Homepage HTML is not oversized

    Homepage HTML is 761 KB.

  • ✓
    Browser caching is allowed

    Pages may be cached by browsers and CDNs.

  • ✓
    Images use a modern format

    All 168 image(s) are JPEG or PNG, with no WebP or AVIF alternative. WebP is typically 25-35% smaller at the same quality and is supported by every current browser — on image-led pages this is usually the single largest saving available, and images are what Largest Contentful Paint measures.

Search fundamentals

The tags, files and signals search engines read first.

21 passed · 11 failed · 3 skipped
74%
  • ✕
    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.

  • ✕
    Homepage title is present and well sizedmedium

    Title is 84 characters. Google truncates around 60 characters, and a title under 10 tells it almost nothing.

    Круглосуточные электрики в Москве ⚡ - Срочно вызвать электрика в любой район. Звони!

    Write 50-60 characters covering what you do and where you do it.

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

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

  • ✕
    Page language declaredlow

    Language attribute present.

    Add lang="en" to the <html> tag.

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

  • ✓
    XML sitemap published

    Sitemap found listing 10 URLs.

  • ✓
    Homepage meta description is present

    Description is 158 characters.

  • ✓
    Homepage canonical is correct

    Canonical points at this page.

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

    10 of 10 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

    5 Open Graph tags found.

  • ✓
    URLs are readable

    URLs use lowercase, hyphenated, extension-free paths.

  • ✓
    Content is not served behind query parameters

    0 of 10 crawled URLs carry query parameters other than tracking tags.

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

22 passed · 3 failed · 1 skipped
89%
  • ✕
    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.

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

  • ✕
    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 10 crawled pages have distinct titles.

  • ✓
    Every page is linked from somewhere

    All 10 crawled pages are reachable by internal links.

  • ✓
    Pages have enough content

    All 10 crawled pages carry substantial content.

  • ✓
    Every page has a meta description

    0 of 10 crawled pages have no meta description.

  • ✓
    Images have alt text

    9 of 285 images across the crawl have no alt attribute. Alt text is how search engines read images and how screen readers describe them.

  • ✓
    Navigation is present on every page

    Every crawled page carries at least three internal links, so navigation is consistently rendered.

  • ✓
    Pages are meaningfully different from each other

    No two crawled pages share substantially the same text.

  • ✓
    No broken internal pages

    All 10 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

    9 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 10 descriptions found are distinct.

  • ✓
    Links describe where they go

    0 of 205 internal link(s) use text like 'click here' or no text at all.

  • ✓
    Every page is linked from another

    Every crawled page is linked from at least one other page.

  • ✓
    No phrase is repeated unnaturally

    No phrase dominates a page's text.

  • ✓
    One H1 per page

    0 of 10 pages do not have exactly one H1 heading.

  • ✓
    No long redirect chains

    No multi-step redirects found.

  • ✓
    Sitemap matches the real site

    Sitemap lists 10 URLs; we reached 10 by crawling. 0 sitemap URLs were not linked from the pages we visited.

  • ✓
    No dead-end pages

    Every crawled page links onward.

  • ✓
    Internal authority is spread, not pooled

    Pages receive 8.4 internal links on average across the crawl, with no single page absorbing most of them.

  • ✓
    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 · 3 failed · 4 skipped
90%
  • ✕
    Lookalike domains are not registeredlow

    1 variant(s) of your domain are registered by someone. None can send mail today, but registration is the first step and adding a mail record takes minutes.

    elektrik24.com

    Monitor these, and register the ones closest to your brand.

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

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

  • –
    Certificate history reviewed

    Not measured — the certificate transparency log was unavailable (returned 502).

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

  • ✓
    No lookalike domain can send mail as your brand

    We generated and checked 60 plausible misspellings and variants of your domain. 1 are registered, but none has mail servers configured, so none can currently send email that appears to be from you.

  • ✓
    Redundant nameservers

    2 nameserver(s) configured.

  • ✓
    No subdomain can be taken over

    Checked 0 subdomain(s); none point at a cloud service that has released them.

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

  • ✓
    Sitemap lastmod dates are meaningful

    10 of 10 sitemap URL(s) carry a lastmod date across 10 distinct value(s).

  • ✓
    Internal links pass authority

    0 internal link(s) are marked nofollow.

  • ✓
    Software versions are not disclosed

    No version numbers advertised in response headers.

  • ✓
    Hosting network identified

    Served from AS57724 (DDOS-GUARD DDOS-GUARD LTD), announced in 185.215.4.0/24 — a block of 256 addresses.

  • ✓
    What this audit examined

    10 page(s) were examined, chosen to cover 3 of the 3 distinct page templates found across 10 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
72%
  • ✕
    Navigation does not depend on JavaScripthigh

    The served HTML exposes 20 internal links and the rendered page 44. 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 20 → rendered 44 internal links

    Emit real <a href> links in the server response for anything that should be crawled and ranked.

  • ✕
    All page resources load successfullymedium

    3 resource(s) failed to load. Missing images and stylesheets are visible to customers; missing scripts break features.

    https://abt.s3.yandex.net/expjs/latest/exp.js (failed)
    https://mc.yandex.ru/metrika/tag.js (failed)
    https://static.tildacdn.com/js/tilda-stat-1.0.min.js (failed)
    3 affected URLs

    Fix or remove these URLs.

  • ✕
    Tap targets are big enough to hitmedium

    22 of 51 tappable element(s) are smaller than 48x48 pixels, and 8 sit closer than 8 pixels to a neighbour. 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.

    To main content (149x39)
    Аварийный (58x36)
    Услуги (35x36)
    Срочно (37x36)
    Контакты (49x36)

    Give tappable elements at least 48x48 CSS pixels and 8 pixels of spacing — usually padding on the link rather than a bigger font.

  • ✕
    The page fits the screenlow

    Content overflows the mobile viewport by 10 pixels, so the page scrolls sideways. It is one of the most visible signs of a broken mobile layout, and Google indexes the mobile version of your site.

    scrollWidth exceeds viewport by 10px at 390px wide

    Find the element wider than the viewport — usually a fixed-width table, image or embed — and constrain it with max-width: 100%.

  • ✕
    Reasonable number of requestslow

    The page made 106 network requests to load. Each is a round trip, and on mobile data they add up quickly.

    Remove unused third-party tags, and combine or lazy-load the rest.

  • ✓
    Content is in the HTML, not built by JavaScript

    The served HTML contains 2936 words and the rendered page 2940 — the content is present before JavaScript runs.

  • ✓
    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.4s on a simulated phone viewport. Google's threshold for 'good' is 2.5s.

  • ✓
    Navigation links are crawlable without JavaScript

    142 links in the served HTML, 148 after rendering — navigation is discoverable.

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

  • ✓
    No excessive JavaScript blocking

    0 long JavaScript task(s) blocked the main thread while loading.

  • ✓
    Body text is legible on a phone

    0 of 500 text block(s) render below 12px on a mobile viewport.

Scan details

Final URLhttps://elektrik-24.com/
Host IPs185.215.4.24
Pages crawled10 of 10 attempted
Sitemap URLs10
Nameserversns1.tildadns.com, ns2.tildadns.com
Mail serversmx1.beget.com, mx2.beget.com
DKIM selectorsnone found
Mail server IPs185.78.30.126, 185.78.30.95, 5.101.158.68
TLSTLSv1.3 · TLS_AES_128_GCM_SHA256 · issued by Let's Encrypt
Detected stackcustom / origin / other-dns
Browser renderCamoufox (stealth Firefox) · 5.7s · 2940 words, 148 links after JavaScript
10 URLs crawled
  • https://elektrik-24.com/
  • https://elektrik-24.com/srochno
  • https://elektrik-24.com/uslugi-elektrika
  • https://elektrik-24.com/elektrik
  • https://elektrik-24.com/elektrik-na-dom
  • https://elektrik-24.com/vyzvat-elektrika
  • https://elektrik-24.com/avarijnyj-elektrik
  • https://elektrik-24.com/vizvat-elektrika-na-dom
  • https://elektrik-24.com/srochnii-vizov-elektrika
  • https://elektrik-24.com/podklyuchenie-doma-k-elektrichestvu

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.

We only email you about this request. No list, no newsletter.

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 elektrik-24.com first.