Tools & Wizards About Us
san-solnechniy.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

san-solnechniy.com

Путевки в санаторий «Солнечный» в Кисловодске для лечения и отдыха, официальный сайт санатория

Page Load Speed

7.4 sec in total

First Response

371 ms

Resources Loaded

6.7 sec

Page Rendered

363 ms

san-solnechniy.com screenshot

About Website

Welcome to san-solnechniy.com homepage info - get ready to check San Solnechniy best content for Russia right away, or after learning these important things about san-solnechniy.com

Официальный сайт санатория в Кисловодске. Выгодные цены, полный комплекс оздоровительных процедур, удобные номера, возможность отдыха всей семьей и проведения конференций — все это в лучшем санатории ...

Visit san-solnechniy.com

Key Findings

We analyzed San-solnechniy.com page load time and found that the first response time was 371 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

san-solnechniy.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

51/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value28.4 s

0/100

10%

TBT (Total Blocking Time)

Value6,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.493

17/100

15%

TTI (Time to Interactive)

Value40.5 s

0/100

10%

Network Requests Diagram

san-solnechniy.com

371 ms

san-solnechniy.com

966 ms

index.css

382 ms

745 ms

travelline-style.css

352 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 68% of them (62 requests) were addressed to the original San-solnechniy.com, 8% (7 requests) were made to Ru-ibe.tlintegration.ru and 5% (5 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain San-solnechniy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 444.1 kB (5%)

Content Size

8.2 MB

After Optimization

7.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of San-solnechniy.com main page is 8.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 7.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 158.3 kB

  • Original 193.1 kB
  • After minification 187.9 kB
  • After compression 34.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 158.3 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 103.5 kB

  • Original 7.1 MB
  • After minification 7.0 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. San Solnechniy images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 113.5 kB

  • Original 799.2 kB
  • After minification 799.2 kB
  • After compression 685.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 113.5 kB or 14% of the original size.

CSS Optimization

-100%

Potential reduce by 68.7 kB

  • Original 69.0 kB
  • After minification 280 B
  • After compression 231 B

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. San-solnechniy.com needs all CSS files to be minified and compressed as it can save up to 68.7 kB or 100% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (59%)

Requests Now

37

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of San Solnechniy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

san-solnechniy.com

san-solnechniy.com

371 ms

san-solnechniy.com

san-solnechniy.com

966 ms

index.css

index.css

382 ms

745 ms

travelline-style.css

travelline-style.css

352 ms

logo-white.svg

logo-white.svg

352 ms

manifest.js

manifest.js

351 ms

vendor.js

vendor.js

934 ms

index.js

index.js

403 ms

mango.js

mango.js

657 ms

full-e375679eab0e00a5e81ddbb027f673d8841bde2c.js

full-e375679eab0e00a5e81ddbb027f673d8841bde2c.js

1906 ms

loader.js

loader.js

673 ms

client.js

client.js

1188 ms

HelveticaNeueCyr-Roman.woff

HelveticaNeueCyr-Roman.woff

132 ms

HelveticaNeueCyr-Medium.woff

HelveticaNeueCyr-Medium.woff

201 ms

HelveticaNeueCyr-Light.woff

HelveticaNeueCyr-Light.woff

162 ms

HelveticaNeueCyr-UltraLight.woff

HelveticaNeueCyr-UltraLight.woff

242 ms

HelveticaNeueCyr-Thin.woff

HelveticaNeueCyr-Thin.woff

293 ms

HelveticaNeueCyr-Bold.woff

HelveticaNeueCyr-Bold.woff

331 ms

HelveticaNeueCyr-Black.woff

HelveticaNeueCyr-Black.woff

360 ms

HelveticaNeueCyr-Heavy.woff

HelveticaNeueCyr-Heavy.woff

400 ms

666ae286d7dd0.jpg

666ae286d7dd0.jpg

1136 ms

666ae5ef05086.jpg

666ae5ef05086.jpg

1560 ms

6606c1a9be304.jpg

6606c1a9be304.jpg

799 ms

65e1920a2bcb8.jpg

65e1920a2bcb8.jpg

1473 ms

660bdc3f29e3f.jpg

660bdc3f29e3f.jpg

1078 ms

660bdc7b3021f.jpg

660bdc7b3021f.jpg

864 ms

gtm.js

gtm.js

64 ms

tag.js

tag.js

875 ms

helveticaneuecyr-roman.woff

helveticaneuecyr-roman.woff

117 ms

helveticaneuecyr-light.woff

helveticaneuecyr-light.woff

202 ms

helveticaneuecyr-medium.woff

helveticaneuecyr-medium.woff

192 ms

helveticaneuecyr-ultralight.woff

helveticaneuecyr-ultralight.woff

189 ms

helveticaneuecyr-roman.woff

helveticaneuecyr-roman.woff

1404 ms

helveticaneuecyr-thin.woff

helveticaneuecyr-thin.woff

188 ms

helveticaneuecyr-bold.woff

helveticaneuecyr-bold.woff

163 ms

helveticaneuecyr-black.woff

helveticaneuecyr-black.woff

148 ms

helveticaneuecyr-light.woff

helveticaneuecyr-light.woff

1511 ms

helveticaneuecyr-medium.woff

helveticaneuecyr-medium.woff

1839 ms

helveticaneuecyr-heavy.woff

helveticaneuecyr-heavy.woff

146 ms

helveticaneuecyr-ultralight.woff

helveticaneuecyr-ultralight.woff

1992 ms

helveticaneuecyr-thin.woff

helveticaneuecyr-thin.woff

1842 ms

helveticaneuecyr-bold.woff

helveticaneuecyr-bold.woff

1937 ms

helveticaneuecyr-black.woff

helveticaneuecyr-black.woff

1918 ms

helveticaneuecyr-heavy.woff

helveticaneuecyr-heavy.woff

2073 ms

lodash.281ba93d.js

lodash.281ba93d.js

130 ms

core-js.e8830056.js

core-js.e8830056.js

392 ms

axios.d7e89cc3.js

axios.d7e89cc3.js

389 ms

ua-parser-js.59d4b581.js

ua-parser-js.59d4b581.js

393 ms

regenerator-runtime.3d4c54f2.js

regenerator-runtime.3d4c54f2.js

400 ms

7392.5f35be5d.js

7392.5f35be5d.js

519 ms

loader.js

loader.js

512 ms

advert.gif

advert.gif

683 ms

loader.js

loader.js

439 ms

sync_cookie_image_decide

sync_cookie_image_decide

141 ms

HelveticaNeueCyr-Roman.ttf

HelveticaNeueCyr-Roman.ttf

710 ms

HelveticaNeueCyr-Light.ttf

HelveticaNeueCyr-Light.ttf

571 ms

1

1

276 ms

widgetsSettings.json

widgetsSettings.json

778 ms

grab.cur

grab.cur

152 ms

grabbing.cur

grabbing.cur

152 ms

help.cur

help.cur

300 ms

zoom_in.cur

zoom_in.cur

417 ms

HelveticaNeueCyr-Medium.ttf

HelveticaNeueCyr-Medium.ttf

246 ms

HelveticaNeueCyr-Thin.ttf

HelveticaNeueCyr-Thin.ttf

219 ms

helveticaneuecyr-roman.ttf

helveticaneuecyr-roman.ttf

117 ms

HelveticaNeueCyr-UltraLight.ttf

HelveticaNeueCyr-UltraLight.ttf

165 ms

HelveticaNeueCyr-Bold.ttf

HelveticaNeueCyr-Bold.ttf

197 ms

HelveticaNeueCyr-Black.ttf

HelveticaNeueCyr-Black.ttf

234 ms

helveticaneuecyr-light.ttf

helveticaneuecyr-light.ttf

116 ms

helveticaneuecyr-roman.ttf

helveticaneuecyr-roman.ttf

985 ms

helveticaneuecyr-medium.ttf

helveticaneuecyr-medium.ttf

117 ms

helveticaneuecyr-thin.ttf

helveticaneuecyr-thin.ttf

117 ms

helveticaneuecyr-light.ttf

helveticaneuecyr-light.ttf

749 ms

helveticaneuecyr-ultralight.ttf

helveticaneuecyr-ultralight.ttf

118 ms

helveticaneuecyr-medium.ttf

helveticaneuecyr-medium.ttf

793 ms

HelveticaNeueCyr-Heavy.ttf

HelveticaNeueCyr-Heavy.ttf

241 ms

helveticaneuecyr-bold.ttf

helveticaneuecyr-bold.ttf

121 ms

helveticaneuecyr-thin.ttf

helveticaneuecyr-thin.ttf

987 ms

helveticaneuecyr-black.ttf

helveticaneuecyr-black.ttf

116 ms

helveticaneuecyr-ultralight.ttf

helveticaneuecyr-ultralight.ttf

888 ms

helveticaneuecyr-bold.ttf

helveticaneuecyr-bold.ttf

998 ms

helveticaneuecyr-black.ttf

helveticaneuecyr-black.ttf

1243 ms

app3.js

app3.js

515 ms

helveticaneuecyr-heavy.ttf

helveticaneuecyr-heavy.ttf

119 ms

helveticaneuecyr-heavy.ttf

helveticaneuecyr-heavy.ttf

1053 ms

iframe.html

iframe.html

681 ms

ui.24.10.3157-f752058.js

ui.24.10.3157-f752058.js

84 ms

vendor.155c7a.js

vendor.155c7a.js

34 ms

services.8d086a.js

services.8d086a.js

23 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

88 ms

Accessibility Review

san-solnechniy.com accessibility score

69

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

san-solnechniy.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

san-solnechniy.com SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise San-solnechniy.com can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that San-solnechniy.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

san-solnechniy.com

Open Graph description is not detected on the main page of San Solnechniy. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: