7 sec in total
470 ms
4.6 sec
1.9 sec
Visit go-smile.ru now to see the best up-to-date Go Smile content for Russia and also check out these interesting facts you probably never knew about go-smile.ru
Оригинальные полоски crest и зубные пасты из США, официальные поставки ирригаторов. покупайте Crest 3d White в магазине Go-smile - это низкие цены, гарантия возврата средств и доставка по всей стране.
Visit go-smile.ruWe analyzed Go-smile.ru page load time and found that the first response time was 470 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
go-smile.ru performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value5.9 s
14/100
25%
Value10.6 s
7/100
10%
Value1,410 ms
15/100
30%
Value0.081
94/100
15%
Value16.1 s
6/100
10%
470 ms
865 ms
473 ms
354 ms
359 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 95% of them (101 requests) were addressed to the original Go-smile.ru, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Go-smile.ru.
Page size can be reduced by 131.4 kB (19%)
683.9 kB
552.5 kB
In fact, the total size of Go-smile.ru main page is 683.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 529.6 kB which makes up the majority of the site volume.
Potential reduce by 61.3 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 61.3 kB or 83% of the original size.
Potential reduce by 16.2 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. Go Smile images are well optimized though.
Potential reduce by 50.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 50.7 kB or 67% of the original size.
Potential reduce by 3.3 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. Go-smile.ru needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 76% of the original size.
Number of requests can be reduced by 24 (23%)
103
79
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Go Smile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
go-smile.ru
470 ms
www.go-smile.ru
865 ms
bootstrap.min.css
473 ms
stylesheet.css
354 ms
fast_order.css
359 ms
owl.carousel.css
359 ms
owl.theme.css
359 ms
jquery-ui-1.8.16.custom.css
359 ms
style.css
504 ms
jquery-1.7.1.min.js
664 ms
bootstrap.min.js
500 ms
jquery-ui-1.8.16.custom.min.js
793 ms
common.js
512 ms
owl.carousel.js
632 ms
script.js
649 ms
ui.totop.css
651 ms
easing.js
659 ms
jquery.ui.totop.js
764 ms
jquery.magnific-popup.min.js
782 ms
magnific-popup.css
786 ms
stylesheet.css
836 ms
ocdev_smart_checkout.js
841 ms
inputmask.js
903 ms
jquery.placeholder.js
911 ms
font-awesome.min.css
922 ms
background-gradient.png
161 ms
header_bg_new.jpg
163 ms
logo_new.png
162 ms
phone.gif
158 ms
cart.png
163 ms
menu-background.png
163 ms
3-1000x319.jpg
791 ms
2-1000x319.jpg
661 ms
1-1000x319.jpg
664 ms
4-1000x319.jpg
789 ms
5-1000x319.jpg
786 ms
1.jpg
512 ms
2.jpg
789 ms
4.jpg
808 ms
1-160x160.jpg
839 ms
stars-4.png
937 ms
2-160x160.jpg
937 ms
3-160x160.jpg
933 ms
stars-5.png
941 ms
5-160x160.jpg
988 ms
6-160x160.jpg
1038 ms
9-160x160.jpg
1139 ms
14-160x160.jpg
1146 ms
24-160x160.jpg
1149 ms
27-160x160.jpg
1168 ms
28-160x160.jpg
1175 ms
29-160x160.jpg
1189 ms
31-160x160.jpg
1276 ms
34-160x160.jpg
1284 ms
35-160x160.jpg
1287 ms
36-160x160.jpg
1304 ms
38-160x160.jpg
1309 ms
39-160x160.jpg
1329 ms
40-160x160.jpg
1422 ms
41-160x160.jpg
1447 ms
42-160x160.jpg
1377 ms
43-160x160.jpg
1322 ms
44-160x160.jpg
1325 ms
45-160x160.jpg
1331 ms
46-160x160.jpg
1403 ms
47-160x160.jpg
1432 ms
glyphicons-halflings-regular.woff
1439 ms
watch.js
173 ms
analytics.js
171 ms
DCaaQflrea
272 ms
collect
41 ms
widget_ru_RU.js
219 ms
index.php
1186 ms
48-160x160.jpg
969 ms
49-160x160.jpg
968 ms
50-160x160.jpg
906 ms
51-160x160.jpg
961 ms
52-160x160.jpg
961 ms
53-160x160.jpg
970 ms
54-160x160.jpg
973 ms
55-160x160.jpg
984 ms
56-160x160.jpg
898 ms
58-160x160.jpg
929 ms
59-160x160.jpg
939 ms
60-160x160.jpg
939 ms
61-160x160.jpg
923 ms
62-160x160.jpg
920 ms
63-160x160.jpg
833 ms
64-160x160.jpg
854 ms
65-160x160.jpg
861 ms
66-160x160.jpg
843 ms
67-160x160.jpg
863 ms
68-160x160.jpg
907 ms
69-160x160.jpg
839 ms
70-160x160.jpg
864 ms
71-160x160.jpg
871 ms
72-160x160.jpg
860 ms
74-160x160.jpg
884 ms
75-160x160.jpg
909 ms
76-160x160.jpg
840 ms
73-160x160.jpg
837 ms
57-160x160.jpg
878 ms
77-160x160.jpg
835 ms
78-160x160.jpg
858 ms
79-160x160.jpg
912 ms
ui.totop.png
875 ms
go-smile.ru accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
go-smile.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
go-smile.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Image elements do not have [alt] attributes
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
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Go-smile.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 Go-smile.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
go-smile.ru
Open Graph description is not detected on the main page of Go Smile. 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: