4.6 sec in total
664 ms
3.6 sec
328 ms
Click here to check amazing Sampo content for Russia. Otherwise, check out these important facts you probably never knew about sampo.ru
Официальный сайт компьютерной сети «Сампо.ру» — лидера рынка услуг доступа в Интернет и цифрового ТВ в Карелии
Visit sampo.ruWe analyzed Sampo.ru page load time and found that the first response time was 664 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
sampo.ru performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value7.3 s
5/100
25%
Value10.2 s
8/100
10%
Value2,250 ms
6/100
30%
Value0.891
3/100
15%
Value14.3 s
9/100
10%
664 ms
536 ms
62 ms
38 ms
280 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sampo.ru, 80% (72 requests) were made to Static.tildacdn.com and 4% (4 requests) were made to Samporu.bitrix24.ru. The less responsive or slowest element that took the longest time to load (988 ms) relates to the external source Optim.tildacdn.com.
Page size can be reduced by 630.4 kB (23%)
2.7 MB
2.1 MB
In fact, the total size of Sampo.ru main page is 2.7 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. 65% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 460.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 460.7 kB or 85% of the original size.
Potential reduce by 19.9 kB
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. Sampo images are well optimized though.
Potential reduce by 89.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 89.7 kB or 17% of the original size.
Potential reduce by 60.1 kB
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. Sampo.ru needs all CSS files to be minified and compressed as it can save up to 60.1 kB or 23% of the original size.
Number of requests can be reduced by 44 (51%)
87
43
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sampo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
sampo.ru
664 ms
go.sampo.ru
536 ms
tilda-fallback-1.0.min.js
62 ms
tilda-grid-3.0.min.css
38 ms
tilda-blocks-page3817930.min.css
280 ms
css2
48 ms
tilda-animation-2.0.min.css
49 ms
tilda-cover-1.0.min.css
52 ms
highlight.min.css
50 ms
tilda-cards-1.0.min.css
50 ms
tilda-forms-1.0.min.css
51 ms
all.cssintegrity=sha384-B4dIYHKNBt8Bc12p+WXckhzcICo0wtJAoU8YZTY5qE0Id1GSseTk6S+L3BlXeVIUcrossorigin=anonymous
114 ms
tilda-polyfill-1.0.min.js
53 ms
jquery-1.10.2.min.js
53 ms
tilda-scripts-3.0.min.js
52 ms
tilda-blocks-page3817930.min.js
361 ms
tilda-lazyload-1.0.min.js
53 ms
tilda-animation-2.0.min.js
53 ms
tilda-zero-1.1.min.js
54 ms
tilda-slds-1.4.min.js
54 ms
hammer.min.js
54 ms
tilda-cover-1.0.min.js
54 ms
highlight.min.js
55 ms
tilda-cards-1.0.min.js
56 ms
tilda-popup-1.0.min.js
56 ms
tilda-forms-1.0.min.js
56 ms
tilda-menusub-1.0.min.js
59 ms
tilda-menu-1.0.min.js
58 ms
tilda-submenublocks-1.0.min.js
58 ms
tilda-animation-ext-1.0.min.js
59 ms
tilda-zero-scale-1.0.min.js
60 ms
tilda-skiplink-1.0.min.js
59 ms
tilda-events-1.0.min.js
59 ms
tilda-fallback-advanced-1.0.min.js
3 ms
white.svg
239 ms
tarif-220-pop-up.svg
275 ms
-30-pop-up.svg
327 ms
-70-pop-up.svg
231 ms
-100-pop-up.svg
269 ms
-300-pop-up.svg
322 ms
_-pop-up.svg
346 ms
-pop-up.svg
662 ms
sampo-logotype-white.svg
668 ms
font
27 ms
go.sampo.ru
196 ms
220-small.svg
220 ms
-30-small.svg
474 ms
-70-small.svg
484 ms
-100-small.svg
486 ms
-300-small.svg
476 ms
_2-small.svg
678 ms
-small.svg
686 ms
dragon-scales.svg
611 ms
loader_1_j97jnf.js
476 ms
tilda-slds-1.4.min.css
2 ms
tilda-popup-1.1.min.css
9 ms
tilda-menusub-1.0.min.css
59 ms
styles.min.css
953 ms
script.min.js
840 ms
form.polyfill.js
212 ms
Asset_1.svg
232 ms
bv7pb55oldaq8p1ovddg.png
565 ms
Succes.svg
429 ms
Asset_9.svg
351 ms
Asset_4.svg
111 ms
Asset_2.svg
187 ms
Asset_5.svg
94 ms
Asset_3.svg
179 ms
photo.svg
217 ms
Group_246.svg
393 ms
Asset_7_1.svg
396 ms
Group_243.svg
384 ms
Asset_1.svg
346 ms
Frame.svg
573 ms
Asset_5.svg
482 ms
Asset_4.svg
604 ms
home-internet.svg
478 ms
chastniy-dom.svg
566 ms
services.svg
598 ms
category.svg
695 ms
dom-tv.svg
570 ms
digital-tv.svg
653 ms
interactive-tv.svg
656 ms
wink.svg
762 ms
combo24.png
988 ms
wink_tab4.png
904 ms
app.js
196 ms
app.bundle.min.css
521 ms
app.bundle.min.js
778 ms
smart-package-image.png
363 ms
sampo.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
Links do not have a discernible name
sampo.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
sampo.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sampo.ru 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 Sampo.ru 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.
sampo.ru
Open Graph data is detected on the main page of Sampo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: