dssl.ru website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 4.6 s

  4.6 s

  Real visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

• Real-user CLS: 0.42

  0.42

  For real visitors the layout shifts by 0.42 (75th percentile). Good is under 0.1.

• Real-user FCP: 3.8 s

  3.8 s

  Real visitors see the first content after 3.8 s (75th percentile). Good is under 1.8 s.

• Real-user TTFB: 2.1 s

  2.1 s

  Real visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

• Largest content (LCP) got 36% slower for real visitors

  +36%

  Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.4 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• 1 image in older formats

  1 image (42 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  Elements (1)

• About 0.4 g of CO₂ per visit

  0.36 g

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

• 1 button without a name

  1 button has no accessible name, so screen readers announce just “button”.

  Elements (1)

• 35 text elements with low contrast

  35 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (3)

• 12 tap targets too small

  12 tap targets are too small or too close together to hit reliably with a finger.

  Elements (3)

• Hidden but focusable

  2 elements hidden from screen readers can still receive keyboard focus.

  Elements (2)

• All page content should be contained by landmarks (77 elements)

  All page content should be contained by landmarks: 77 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• Zoom is disabled

  The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  Elements (1)

• 8 form fields without a label

  8 form fields have no label, so screen readers announce an empty box and autofill guesses.

  View source

• 7 links without text

  7 visible links have no text or label, so screen readers cannot say where they go.

  Elements (3)

• Title is long (93 characters)

  Your title is 93 characters, so Google will cut it off around 60: “Системы видеонаблюдения: проектирование, производство, продажа оборудования для охранных …”.

  View source

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

• Meta description is long (305 characters)

  Your meta description is 305 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

• 768 internal links, 18 external

  The homepage links to 768 pages on dssl.ru and 18 external pages.

• 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 /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 linked page is broken

  Your homepage links to /catalog/compare.php, which answers with an error. Visitors hit a dead end and search engines drop it.

  Elements (1)

• 1 page without an H1

  /products/kamery-videonablyudeniya has no <h1> headline, so visitors and search engines get no clear main topic.

• 10 pages slow to respond

  /about/stores/131162, /integratoram/price, /products/moduli-i-potrassir, /products/kamery-videonablyudeniya, /products/teplovizionnoe-oborudovanie and /products/setevoe-oborudovanie and 4 others took over 3 s to send their HTML from our server.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 195 found) and read each the way a search engine does.

• 18 small tap targets

  18 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

• 1 broken external link

  1 link to other sites is dead, for example https://confluence.trassir.com/pages/viewpage.action?pageId=36864630&roistat_visit=12088083 (404).

• No HSTS header

  No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• HTTP/1.1 only

  The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  dssl.ru has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• 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 analytics detected

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

• Only about 225 words

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

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

• No DMARC policy

  dssl.ru has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

• Email authentication score: 45/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

• 24 cookies set on arrival

  24

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

• 16 other companies contacted

  Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.