4.2 sec in total
850 ms
3 sec
276 ms
Click here to check amazing 3 15 content for Russia. Otherwise, check out these important facts you probably never knew about 3-15.ru
Наручные часы популярных мировых брендов в каталоге интеренет-магазина 3-15. Только оригинальные модели. Все бренды подтверждены сертификатами от официальных дистрибьютеров в России. Большой выбор час...
Visit 3-15.ruWe analyzed 3-15.ru page load time and found that the first response time was 850 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
3-15.ru performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value5.2 s
23/100
25%
Value4.0 s
81/100
10%
Value380 ms
70/100
30%
Value0.032
100/100
15%
Value4.0 s
88/100
10%
850 ms
283 ms
189 ms
194 ms
197 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 73% of them (99 requests) were addressed to the original 3-15.ru, 9% (12 requests) were made to Vk.com and 3% (4 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain 3-15.ru.
Page size can be reduced by 1.1 MB (39%)
2.9 MB
1.8 MB
In fact, the total size of 3-15.ru main page is 2.9 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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 65.6 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 65.6 kB or 80% of the original size.
Potential reduce by 161.7 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. 3 15 images are well optimized though.
Potential reduce by 650.8 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 650.8 kB or 72% of the original size.
Potential reduce by 270.9 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. 3-15.ru needs all CSS files to be minified and compressed as it can save up to 270.9 kB or 83% of the original size.
Number of requests can be reduced by 49 (40%)
121
72
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 3 15. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
3-15.ru
850 ms
bootstrap.min.css
283 ms
bootstrap-modifed.css
189 ms
slick.css
194 ms
fonts.css
197 ms
jquery-2.1.4.min.js
296 ms
bootstrap.min.js
201 ms
slick.min.js
294 ms
jquery.debounce-1.0.5.js
294 ms
jquery.maskedinput-1.4.1.min.js
317 ms
angular-1.2.15.min.js
497 ms
angular-local-storage.js
374 ms
core.css
374 ms
style.css
387 ms
style.css
385 ms
styles.css
389 ms
template_styles.css
471 ms
core.js
560 ms
core_ajax.js
482 ms
session.js
482 ms
jquery.fancybox.css
486 ms
app.js
572 ms
catalogFilter.js
578 ms
catalogProvider.js
580 ms
prodItem.js
584 ms
scripts.js
591 ms
wild_3d.min.js
652 ms
jquery.elevateZoom-3.0.8.min.js
663 ms
script.js
674 ms
jquery.fancybox.pack.js
674 ms
openapi.js
395 ms
api.js
409 ms
sprite.png
199 ms
logo.png
200 ms
banner-1-onelink.jpg
685 ms
banner-2-onelink.jpg
203 ms
b0e379004da1c5ebbe69825f251f4202.jpg
201 ms
cd6e08ba79701071877a3ad64529e44a.jpg
200 ms
9bac98b33d6fed4c5bc63fa8502c4d67.jpg
202 ms
0d0bca064392bb470c9b664532bf754c.jpg
203 ms
f55f2ac8f75e52db19c42c3eda26dc81.jpg
204 ms
18fb585a9fe67936bd2eb6f0390e855d.jpg
222 ms
4a7b2e70ad288cbabfcd8e67914f0bd0.jpg
283 ms
esprit.jpg
289 ms
fossil.jpg
293 ms
2d022516b72efa52e9a39fe8be7c2184.jpg
296 ms
8ba6f0f047e3c3604fe0d9ec4e5dc19b.jpg
300 ms
j_chevalier.jpg
376 ms
6c35959a73cbff267fc1e4528afc835b.jpg
392 ms
2a9b3e7347b9c9197e8c4f0f3b85d133.jpg
392 ms
4083ceb764584f42bc21bd1dc60a5692.jpg
395 ms
352bfdd4472c102ba29aa324e47c7e71.jpg
397 ms
f35e9a9ccd3829c3b5ef874dd58bed09.jpg
471 ms
441fb398d93e80f6fa56234edd5bd98f.jpg
480 ms
puma.jpg
485 ms
reebok.jpg
493 ms
8c66580122bf33fcaa207606c4834630.jpg
498 ms
f4b146cf6a6cfd2580ca0904f5cc0503.jpg
566 ms
682b5f8c0d1da1dc6db053c47ed1b050.jpg
576 ms
sainthonore.jpg
586 ms
fb8e549c0bc72d4af7f3b40891b99e97.jpg
592 ms
90dc456dbb26006a6d4fccbef58ffaf0.jpg
596 ms
ec621d1fbc8eb1644560e30758bfe668.jpg
668 ms
06bad23cb02714c216427790f0f8b1be.jpg
671 ms
9b1f33c3ba62ffbddf6dd3dcb04047f2.jpg
678 ms
7b8549e5df1144266ea8e8989edb93d1.jpg
689 ms
untitled_4.png
1028 ms
p.min.js
195 ms
untitled_5_2.png
929 ms
upload.gif
158 ms
widget_community.php
286 ms
client.js
236 ms
watch.js
179 ms
analytics.js
151 ms
analytics.js
256 ms
GothamProRegular.woff
592 ms
GothamProLight.woff
591 ms
GothamProMedium.woff
591 ms
GothamProBold.woff
695 ms
GothamProBlack.woff
671 ms
glyphicons-halflings-regular.woff
680 ms
basket.php
709 ms
942 ms
collect
15 ms
lk_profile.php
782 ms
watch.js
431 ms
211 ms
collect
70 ms
untitled_2.png
802 ms
3_iv67q1033-sm-wh_3.png
814 ms
1_1654.png
1068 ms
discont.png
803 ms
icon1.png
830 ms
analytics.js
263 ms
ga-audiences
44 ms
loader_nav19127_3.js
134 ms
lite.css
132 ms
lite.js
435 ms
lang3_0.js
256 ms
widget_community.css
257 ms
xdm.js
257 ms
al_community.js
262 ms
icon2.png
807 ms
jsonp
206 ms
icon3.png
805 ms
icon4.png
810 ms
prom1.jpg
834 ms
prom2.jpg
941 ms
pixel
17 ms
pixel
18 ms
pixel
19 ms
pixel
16 ms
match
318 ms
prom3.jpg
909 ms
vk.png
812 ms
fb.png
814 ms
instagram.png
831 ms
mastercard.png
890 ms
visa.png
831 ms
yandex.png
848 ms
webmoney.png
847 ms
qiwi.png
863 ms
silver-card.jpg
882 ms
advert.gif
84 ms
px_trans.gif
199 ms
gold-card.jpg
817 ms
30-day-gray.png
822 ms
prom4.png
847 ms
arrows.png
850 ms
7bbEtAOttx8.jpg
264 ms
fBGNym9pOQs.jpg
385 ms
e_736e5f37.jpg
403 ms
qOCMLOc7cE8.jpg
403 ms
camera_50.png
131 ms
w_logo.png
134 ms
1
85 ms
3-15.ru accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
3-15.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
3-15.ru SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 3-15.ru can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 3-15.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.
3-15.ru
Open Graph description is not detected on the main page of 3 15. 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: