3 sec in total
287 ms
2.5 sec
224 ms
Click here to check amazing PIERCINGLINE content for Italy. Otherwise, check out these important facts you probably never knew about piercingline.com
Erlebe die große Auswahl von PIERCINGLINE » Hochwertige Qualität ✓ Schneller Versand ✓ Neueste Trends » Jetzt entdecken!
Visit piercingline.comWe analyzed Piercingline.com page load time and found that the first response time was 287 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
piercingline.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value6.2 s
11/100
25%
Value9.7 s
11/100
10%
Value4,680 ms
0/100
30%
Value0.001
100/100
15%
Value15.6 s
6/100
10%
287 ms
552 ms
326 ms
210 ms
673 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 61% of them (45 requests) were addressed to the original Piercingline.com, 4% (3 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (820 ms) belongs to the original domain Piercingline.com.
Page size can be reduced by 1.1 MB (54%)
2.0 MB
928.9 kB
In fact, the total size of Piercingline.com main page is 2.0 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. 50% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 85.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. This page needs HTML code to be minified as it can gain 14.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 85.7 kB or 74% of the original size.
Potential reduce by 23.5 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. PIERCINGLINE images are well optimized though.
Potential reduce by 909.1 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 909.1 kB or 74% of the original size.
Potential reduce by 77.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. Piercingline.com needs all CSS files to be minified and compressed as it can save up to 77.6 kB or 82% of the original size.
Number of requests can be reduced by 39 (58%)
67
28
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PIERCINGLINE. 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 7 to 1 for CSS and as a result speed up the page load time.
piercingline.com
287 ms
www.piercingline.com
552 ms
jquery-1.7.2.min.js
326 ms
jquery.inputlabel.js
210 ms
jquery-ui.js
673 ms
jquery.simplyscroll.js
215 ms
jquery.jcarousel.min.js
217 ms
jquery.unveil.js
216 ms
jquery.sharrre.min.js
318 ms
e-vendo.js
322 ms
jquery.flexslider.js
338 ms
responsive.js
337 ms
venobox.min.js
424 ms
xmas.js
428 ms
general.css
431 ms
styles.css
537 ms
responsive.css
434 ms
flexslider.css
529 ms
formate.css
536 ms
venobox.css
537 ms
css
25 ms
jquery.dd.js
540 ms
ffsuggest.list.jquery.jsonp.js
634 ms
e-vendo_rde.js
550 ms
addthis_widget.js
9 ms
conversion.js
20 ms
ga.js
12 ms
fbds.js
126 ms
slide_supersale-eh.jpg
337 ms
XADCD000869204A41368D50DBAA611939.gif
639 ms
slide_diamantoptik.jpg
320 ms
slide_bananabell4.jpg
258 ms
slide_byo1.jpg
421 ms
slide_hauptkatalog.jpg
258 ms
slide_uv-fake-septum.jpg
339 ms
slide_echtgold2.jpg
450 ms
button_jobs.jpg
355 ms
button_newsletter.jpg
423 ms
button_bauchnabelpiercing.jpg
543 ms
button_schmuck.jpg
545 ms
button_sale.jpg
561 ms
mailto.png
526 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
10 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
10 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
10 ms
inpage_linkid.js
9 ms
icon-sprite.png
820 ms
piercingline.png
537 ms
__utm.gif
21 ms
schatten-hor.png
593 ms
schatten-vert.png
601 ms
collect
138 ms
test.gif
388 ms
fb-like-box.png
597 ms
11403.js
652 ms
all.js
143 ms
fql
140 ms
145 ms
XADCD000869204A41368D50DBAA611939.js
132 ms
bat.js
76 ms
300lo.json
89 ms
408.b7f7305846701647c20b.js
22 ms
de.gif
473 ms
en.gif
478 ms
dd_arrow.gif
547 ms
72 ms
sh.7c7179124ea24ac6ba46caac.html
51 ms
30 ms
xd_arbiter.php
147 ms
xd_arbiter.php
249 ms
45 ms
rde.js
318 ms
logo
213 ms
2367b18d3c56a66ab806774b3f25cf79
224 ms
piercingline.com 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 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
piercingline.com 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
Missing source maps for large first-party JavaScript
piercingline.com SEO score
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
N/A
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Piercingline.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Piercingline.com main page’s claimed encoding is iso-8859-1. 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.
piercingline.com
Open Graph description is not detected on the main page of PIERCINGLINE. 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: