4 sec in total
304 ms
3.5 sec
263 ms
Click here to check amazing PIERCINGLINE content. Otherwise, check out these important facts you probably never knew about piercingline.de
Erlebe die große Auswahl von PIERCINGLINE » Hochwertige Qualität ✓ Schneller Versand ✓ Neueste Trends » Jetzt entdecken!
Visit piercingline.deWe analyzed Piercingline.de page load time and found that the first response time was 304 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
piercingline.de performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value12.1 s
0/100
25%
Value9.2 s
13/100
10%
Value880 ms
32/100
30%
Value0.027
100/100
15%
Value12.5 s
14/100
10%
304 ms
558 ms
326 ms
210 ms
673 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Piercingline.de, 61% (46 requests) were made to Piercingline.com and 4% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Widgets.trustedshops.com.
Page size can be reduced by 1.1 MB (53%)
2.1 MB
956.1 kB
In fact, the total size of Piercingline.de main page is 2.1 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.3 MB which makes up the majority of the site volume.
Potential reduce by 85.5 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.2 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.5 kB or 74% of the original size.
Potential reduce by 26.0 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 73% of the original size.
Potential reduce by 77.2 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.de needs all CSS files to be minified and compressed as it can save up to 77.2 kB or 83% of the original size.
Number of requests can be reduced by 39 (57%)
69
30
The browser has sent 69 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.de
304 ms
www.piercingline.com
558 ms
jquery-1.7.2.min.js
326 ms
jquery.inputlabel.js
210 ms
jquery-ui.js
673 ms
jquery.simplyscroll.js
210 ms
jquery.jcarousel.min.js
215 ms
jquery.unveil.js
212 ms
jquery.sharrre.min.js
314 ms
e-vendo.js
316 ms
jquery.flexslider.js
423 ms
responsive.js
319 ms
venobox.min.js
421 ms
xmas.js
421 ms
general.css
425 ms
styles.css
433 ms
responsive.css
528 ms
flexslider.css
529 ms
formate.css
536 ms
venobox.css
531 ms
css
27 ms
jquery.dd.js
539 ms
ffsuggest.list.jquery.jsonp.js
634 ms
e-vendo_rde.js
544 ms
addthis_widget.js
20 ms
conversion.js
20 ms
ga.js
29 ms
fbds.js
21 ms
slide_supersale-eh.jpg
440 ms
XADCD000869204A41368D50DBAA611939.gif
657 ms
slide_diamantoptik.jpg
321 ms
slide_bananabell4.jpg
325 ms
slide_byo1.jpg
259 ms
slide_hauptkatalog.jpg
319 ms
slide_uv-fake-septum.jpg
336 ms
slide_echtgold2.jpg
467 ms
button_jobs.jpg
426 ms
button_newsletter.jpg
428 ms
button_bauchnabelpiercing.jpg
430 ms
button_schmuck.jpg
540 ms
button_sale.jpg
632 ms
mailto.png
532 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
18 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
17 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
18 ms
204 ms
inpage_linkid.js
13 ms
icon-sprite.png
708 ms
piercingline.png
511 ms
__utm.gif
15 ms
schatten-hor.png
517 ms
collect
174 ms
schatten-vert.png
573 ms
test.gif
334 ms
fb-like-box.png
581 ms
11403.js
729 ms
all.js
57 ms
fql
124 ms
131 ms
XADCD000869204A41368D50DBAA611939.js
1805 ms
bat.js
214 ms
300lo.json
588 ms
431.3f3d2c347f3364c00f9f.js
45 ms
de.gif
438 ms
en.gif
465 ms
dd_arrow.gif
528 ms
sh.8e5f85691f9aaa082472a194.html
36 ms
96 ms
xd_arbiter.php
24 ms
xd_arbiter.php
34 ms
45 ms
rde.js
348 ms
e611c99c04fda44f56162d094efb70d2
223 ms
logo
222 ms
Chirurgenstahl-Ringoeffnungszange-KLEIN-PG01_s_0.JPG
108 ms
PIERCINGLINE-Neuheiten-Katalog-2016-NK2016_s_0.JPG
108 ms
piercingline.de 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.
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.
piercingline.de 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
Page has valid source maps
piercingline.de 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
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.de 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.de 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.de
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: