15.1 sec in total
525 ms
14.2 sec
371 ms
Welcome to piercingmarket.ru homepage info - get ready to check Piercingmarket best content for Russia right away, or after learning these important things about piercingmarket.ru
Украшения для любых видов пирсинга в розницу и оптом купить в магазине Пирсингмаркет. Выбирайте свой пирсинг из 6000 украшений на нашем сайте. Бесплатная доставка заказов от 1500 рублей. Скидки и бону...
Visit piercingmarket.ruWe analyzed Piercingmarket.ru page load time and found that the first response time was 525 ms and then it took 14.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
piercingmarket.ru performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value5.1 s
25/100
25%
Value6.6 s
37/100
10%
Value2,030 ms
7/100
30%
Value0.019
100/100
15%
Value9.8 s
28/100
10%
525 ms
1038 ms
664 ms
396 ms
397 ms
Our browser made a total of 220 requests to load all elements on the main page. We found that 69% of them (151 requests) were addressed to the original Piercingmarket.ru, 25% (56 requests) were made to St6-21.vk.com and 3% (6 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Piercingmarket.ru.
Page size can be reduced by 1.1 MB (23%)
4.6 MB
3.5 MB
In fact, the total size of Piercingmarket.ru main page is 4.6 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.8 MB which makes up the majority of the site volume.
Potential reduce by 421.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. This page needs HTML code to be minified as it can gain 58.3 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 421.6 kB or 90% of the original size.
Potential reduce by 307.1 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. Obviously, Piercingmarket needs image optimization as it can save up to 307.1 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 252.2 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 252.2 kB or 15% of the original size.
Potential reduce by 76.6 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. Piercingmarket.ru needs all CSS files to be minified and compressed as it can save up to 76.6 kB or 13% of the original size.
Number of requests can be reduced by 83 (40%)
208
125
The browser has sent 208 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Piercingmarket. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
piercingmarket.ru
525 ms
piercingmarket.ru
1038 ms
shop.css
664 ms
custom.css
396 ms
mi.min.css
397 ms
frontend.css
398 ms
frontend_features.css
398 ms
jquery-1.11.1.min.js
922 ms
jquery-migrate-1.2.1.min.js
792 ms
frontend.js
791 ms
frontend_features.js
792 ms
flexdiscountFrontend.js
795 ms
jquery-ui.css
14 ms
jquery-ui.js
22 ms
itemsetsFrontend.css
1092 ms
itemsetsFrontend.js
1187 ms
itemsetsFrontendLocale.js
1188 ms
hideskus.js
1190 ms
main.js
1224 ms
main.css
1317 ms
bootstrap.min.js
1399 ms
jquery.cookie.min.js
1398 ms
slick.min.js
1401 ms
jquery.lazyload.min.js
1397 ms
site.js
1403 ms
lazy.load.js
1529 ms
jQuery.Brazzers-Carousel.min.js
1792 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
233 ms
neformarket.ico
669 ms
mylogo.png
933 ms
vk.png
930 ms
30425.300.jpg
933 ms
30424.300.jpg
934 ms
30411.300.jpg
1076 ms
30403.300.jpg
1213 ms
30398.300.jpg
1207 ms
30392.300.jpg
1213 ms
30386.300.jpg
1214 ms
30383.300.jpg
1343 ms
30375.300.jpg
1607 ms
30368.300.jpg
1607 ms
30254.300.jpg
1744 ms
30229.300.png
1745 ms
30231.300.jpg
1610 ms
30220.300.png
2266 ms
30201.300.png
2659 ms
30193.300.jpg
2003 ms
30187.300.jpg
2005 ms
30179.300.jpg
2133 ms
30169.300.jpg
2269 ms
30161.300.jpg
2417 ms
30156.300.jpg
2416 ms
30150.300.jpg
2679 ms
30134.300.jpg
2815 ms
30123.300.jpg
2813 ms
30110.300.jpg
2944 ms
30103.300.jpg
2683 ms
css
33 ms
MaterialIcons-Regular.woff
3177 ms
30082.300.png
2803 ms
30074.300.png
2982 ms
30066.300.png
3069 ms
30058.300.png
2975 ms
image_280.jpg
2946 ms
image_281.jpg
2881 ms
watch.js
2 ms
image_282.jpg
3009 ms
top100.js
931 ms
flexmenu.min.js
2753 ms
jquery.retina.min.js
2881 ms
image_283.png
2882 ms
image_284.jpg
2903 ms
image_285.jpg
2868 ms
widget_community_messages.php
305 ms
image_301.jpg
2870 ms
image_300.jpg
2866 ms
image_303.jpg
2997 ms
image_302.jpg
2997 ms
image_298.jpg
2897 ms
loader_nav21112336040_3.js
267 ms
fonts_cnt.c7a76efe.css
988 ms
lite.6d09ff63.css
770 ms
lang3_2.js
681 ms
c3d11fba.093082a5.js
655 ms
community_messages.js
663 ms
vkcom-kit.b9457c14.css
851 ms
vkcom-kit.7c3597b4.js
1081 ms
react.6a15a5cc.js
913 ms
vkcom-kit-icons.6494715b.js
979 ms
vkui.1926d43a.js
1142 ms
state-management.a46c500d.js
1040 ms
architecture-mobx.b1015542.js
1080 ms
audioplayer-lib.93b52d88.css
1067 ms
audioplayer-lib.18822298.js
1242 ms
palette.c6252453.css
1153 ms
palette.d4043e4c.js
1175 ms
sticker-lib.72942183.css
1166 ms
sticker-lib.933743cc.js
1231 ms
bootstrap.a54815cb.js
1287 ms
core_spa.c7f6a9bc.js
1272 ms
common.14f5502d.js
1395 ms
f371ea0d.dbc1865d.js
1320 ms
782f47a3.38fd93c4.js
1334 ms
39820787.4128def5.js
1362 ms
fc936a0f.a6371a57.js
1371 ms
f3627a66.8147bddf.js
1438 ms
emoji.ba9ac3c7.css
1422 ms
emoji.9f8d52d9.js
1452 ms
7f463667.b3f6bf8c.js
1456 ms
ui_common.43d06ff5.css
1480 ms
ui_common.78ba6732.js
1516 ms
b691fd56.fcad13bf.js
1553 ms
ui_media_selector.43d06ff5.css
1539 ms
ui_media_selector.d8edf233.js
1540 ms
xdm.js
1565 ms
f528815f.082e1657.js
1614 ms
upload.ade04c10.js
1624 ms
lang3_0.js
753 ms
image_299.jpg
2733 ms
image_278.jpg
2866 ms
image_279.jpg
2865 ms
image_293.jpg
2864 ms
image_276.jpg
2864 ms
lite.bcf10ece3464fec8b554bde483fa2494.js
233 ms
image_99.jpg
2763 ms
image_272.jpg
2858 ms
stickers.69dc6c3d.css
973 ms
vkui.25d6bec9.css
1013 ms
image_273.jpg
2735 ms
widget_community_messages.06a7f227.css
880 ms
notifier.fcca6e68.css
858 ms
image_274.jpg
2605 ms
image_275.jpg
2865 ms
ui_common.54e472db.css
800 ms
ui_media_selector.2e6f2ad1.css
738 ms
base.c26e5b58.css
711 ms
image_104.jpg
2588 ms
image_404.jpg
2875 ms
stickers.632cc4ae.js
732 ms
openapi.js
744 ms
image_259.jpg
2600 ms
image_261.jpg
2586 ms
image_262.jpg
2454 ms
image_263.jpg
2585 ms
image_264.jpg
2711 ms
image_427.jpg
2710 ms
image_265.jpg
2585 ms
qBkJLxFRzZqiqIWQkCrwRvB96vuAyKrlyA2xI0MauFeBLiuBBJMWo7U6umxUlbo-NXw_EEya.jpg
430 ms
QulWsGFAn5k.png
633 ms
w_chat_icon.png
94 ms
w_chat_logo.png
90 ms
widgets_logo_white.svg
91 ms
chats.png
88 ms
community_messages_widget_small_logo.svg
83 ms
emoji_smile_icon.svg
165 ms
upload.gif
173 ms
roboto400.woff
223 ms
roboto500.woff
232 ms
roboto300.woff
221 ms
roboto700.woff
332 ms
image_266.jpg
2408 ms
image_267.jpg
2431 ms
image_286.jpg
2450 ms
image_287.jpg
2576 ms
image_260.jpg
2555 ms
image_268.jpg
2504 ms
image_270.jpg
2379 ms
image_289.jpg
2386 ms
image_288.jpg
2380 ms
image_421.jpg
2505 ms
image_407.jpg
2602 ms
image_408.jpg
2640 ms
image_423.jpg
2376 ms
image_424.jpg
2397 ms
image_304.jpg
2378 ms
image_305.jpg
2505 ms
image_96.jpg
2599 ms
image_290.jpg
2510 ms
image_426.jpg
2398 ms
image_15.jpg
2502 ms
image_291.jpg
2374 ms
image_363.jpg
2501 ms
image_92.jpg
2599 ms
dummy200.png
2377 ms
ajax-loader.gif
2396 ms
30063.300.jpg
2502 ms
30064.300.jpg
2372 ms
30065.300.jpg
2373 ms
30067.300.png
2506 ms
30055.300.jpg
2394 ms
30056.300.jpg
2490 ms
30057.300.jpg
2474 ms
30059.300.png
2369 ms
30426.300.jpg
2502 ms
30427.300.jpg
2398 ms
30428.300.png
2885 ms
30421.300.jpg
2627 ms
30422.300.jpg
2474 ms
30423.300.png
2758 ms
30412.300.jpg
2500 ms
30413.300.jpg
2397 ms
30414.300.jpg
2500 ms
30415.300.jpg
2628 ms
30404.300.jpg
2874 ms
30405.300.jpg
2782 ms
30406.300.jpg
2621 ms
30407.300.jpg
2505 ms
30399.300.jpg
2630 ms
30400.300.jpg
2869 ms
30401.300.jpg
2754 ms
30402.300.png
3156 ms
30396.300.jpg
2633 ms
30394.300.jpg
2530 ms
30395.300.png
3023 ms
print.css
132 ms
social.min.css
397 ms
fontface.css
396 ms
fontello.woff
399 ms
alsrubl-arial-regular.woff
395 ms
alsrubl-arial-bold.woff
437 ms
piercingmarket.ru accessibility score
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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
piercingmarket.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
piercingmarket.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Piercingmarket.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 Piercingmarket.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.
piercingmarket.ru
Open Graph description is not detected on the main page of Piercingmarket. 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: