3 sec in total
107 ms
2.6 sec
331 ms
Click here to check amazing Pril content for Germany. Otherwise, check out these important facts you probably never knew about pril.de
Entdecken Sie die Spülmittel von Pril. Besuchen Sie Pril.de für weitere Informationen über unsere Produkte und Frische-Tipps.
Visit pril.deWe analyzed Pril.de page load time and found that the first response time was 107 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
pril.de performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value9.7 s
0/100
25%
Value5.1 s
62/100
10%
Value290 ms
79/100
30%
Value0.002
100/100
15%
Value10.2 s
25/100
10%
107 ms
239 ms
1694 ms
480 ms
34 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 98% of them (65 requests) were addressed to the original Pril.de, 2% (1 request) were made to Liveux.cnwebperformance.biz. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Pril.de.
Page size can be reduced by 739.9 kB (37%)
2.0 MB
1.2 MB
In fact, the total size of Pril.de 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. 30% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 159.8 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 42.6 kB, which is 23% 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 159.8 kB or 87% of the original size.
Potential reduce by 24.3 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. Pril images are well optimized though.
Potential reduce by 445.3 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 445.3 kB or 85% of the original size.
Potential reduce by 110.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. Pril.de needs all CSS files to be minified and compressed as it can save up to 110.6 kB or 89% of the original size.
Number of requests can be reduced by 60 (97%)
62
2
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pril. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
pril.de
107 ms
pril.de
239 ms
www.pril.de
1694 ms
collector.min.js
480 ms
tracking.lc-ec5c328f716e4ecebe3ccd756f9b5be7-lc.min.js
34 ms
adobeanalytics.lc-30a9b6e333c3a86ade260e4846e3f86c-lc.min.js
76 ms
googleanalytics.lc-c33889da18c44f5abaa265d44c42ace9-lc.min.js
81 ms
accessibility.lc-b6e9c7ff325738db34f51f46ea8dcad8-lc.min.css
69 ms
type.lc-574ff660448db11fbe29711e628ee6f3-lc.min.css
51 ms
visibility.lc-dc4ecb155d6661d0a6f4626a78cf083f-lc.min.css
88 ms
grid.lc-fcfdd819d7c82054a3018071615b5e5a-lc.min.css
74 ms
color.lc-35952be2ba99f7608438e32bb2b1e079-lc.min.css
76 ms
publish.lc-73f568a1ad3e7a1d2487512f373c8848-lc.min.css
126 ms
scriptinjector.lc-a3fb1ca119fd424c9536e99bd55b1923-lc.min.js
95 ms
header.lc-09cde3e778b860c2ca84e21b485f423b-lc.min.css
98 ms
layout1.lc-dd0cfafd7adbbd6bf5e903f33c1417ce-lc.min.css
106 ms
layout1.lc-4cc75683b99ba25a733220377e6658d7-lc.min.css
124 ms
layout2.lc-cc460282c325dd8adbe6ee8e84313edd-lc.min.css
145 ms
image.lc-a47fac35057018c91617baeadb541ebb-lc.min.css
142 ms
logo.lc-b0b4f726ac8091d0fb1b31aa22d7f046-lc.min.css
143 ms
image.lc-f87e5aba969b5e481141f27e60d03aae-lc.min.js
145 ms
modal.lc-2babfe7956717ac1138b18e3f12fedf4-lc.min.css
148 ms
icon.lc-6edca3f10c67b2665376db0a499d829e-lc.min.css
148 ms
navigation.lc-66a200b0c524040e1f2d73b8540f3e23-lc.min.css
146 ms
adjustablenavigation.lc-c53b6babf2697c2e28c97a4c39d8dd18-lc.min.css
150 ms
columncontrol.lc-b81cfee5341eeefef81d750121df023b-lc.min.css
151 ms
accordion.lc-f4e0d553bc5efcfe8e3d9192abcb4841-lc.min.css
165 ms
linklist.lc-582da7c13cb0ba4a623a8efb734791f7-lc.min.css
172 ms
navigationlinklist.lc-ccf4dfd43fb22bdf232413d6554cafa3-lc.min.css
165 ms
accordion.lc-037cad9977c85205b0c23f5e2939969e-lc.min.js
168 ms
modal.lc-ca0c1e5a5359f40529422f0ab81ca83c-lc.min.js
181 ms
modalcontrol.lc-e92d5b3a62de1b59ff920321dac0bd21-lc.min.js
172 ms
setactivelink.lc-c5ac23d9642c0fbb719fd7e21a8980c5-lc.min.js
203 ms
linklist.lc-fdf4aa587dcc73a138e9b5c1f62578c5-lc.min.js
187 ms
navigation.lc-5a46bd604806850b93cd54d7c85ab6d7-lc.min.js
187 ms
searchbutton.lc-57709ef534b493e3f3bcf52fd2145125-lc.min.css
201 ms
treeshaking.lc-386e13d91915a4bceb807f458250b7ad-lc.min.js
199 ms
vendors.lc-2bf956fee0383c86a4254452fe1018a4-lc.min.js
200 ms
notifications.lc-81ca815e865ee8cd0475dcc2147ea8fe-lc.min.css
216 ms
breadcrumb.lc-d0872b6d4e50bbf1e0acac46e2fd872f-lc.min.css
193 ms
section.lc-dea499dc038ea17488f6096e2382484e-lc.min.css
182 ms
calltoaction.lc-8ac6cea318a737d40198a8c823c6e33f-lc.min.css
185 ms
carousel.lc-71b59dfb7ce96596bdaf39df1036fc62-lc.min.css
158 ms
stage.lc-a29c0b567f890601a548875695ac2b50-lc.min.css
182 ms
tooltip.lc-3bf987c076658bd5a77fd9bb338bebbc-lc.min.css
178 ms
text.lc-1452138208d829f0e14a55b5782a91c6-lc.min.css
187 ms
copytoclipboard.lc-3cce0cc2bc051a0f74e88d749f6adadd-lc.min.css
167 ms
title.lc-2c64f0a10f6e2cab0291aecd50997db5-lc.min.css
365 ms
background.lc-b13aab65bf38954ff973bf2f4e321134-lc.min.css
175 ms
footer.lc-615c34bbc226c7d0cddc5e9f08368deb-lc.min.css
174 ms
inlinesection.lc-d61b2ddc27aefe229fd3689e657070e1-lc.min.css
174 ms
backtotop.lc-0f83eae2ae97ef1ddea48c2c04cf4e70-lc.min.css
164 ms
api.lc-b5cfc0d567ebd27d5e002c0db8608ce3-lc.min.js
159 ms
search.lc-f40f77e9b9c5fa70d68c4f646ead5103-lc.min.js
160 ms
search.lc-9fc88f5a09c386cd9610b519ee0b64b6-lc.min.js
161 ms
searchbutton.lc-25928cb644eddc24bf2238bfad0949d9-lc.min.js
167 ms
notifications.lc-e4a5cbaf3a13a77c3c099131c1f2a807-lc.min.js
172 ms
copytoclipboard.lc-6f8fb63583a80324134fcde820505bdb-lc.min.js
173 ms
tooltip.lc-4516e04176dd51af91375519441fde89-lc.min.js
191 ms
carousel.lc-ce155492fb4f7ac59dda883aa00e3a30-lc.min.js
174 ms
backtotop.lc-5c0a2061c41afdf7cf08887694a626cb-lc.min.js
367 ms
redirectflow.lc-10eb6693294d9e55f7eb170e38181903-lc.min.js
173 ms
animations.lc-6f6d50fbac18c5f6a024be1a4ac890e2-lc.min.js
187 ms
publish.lc-4a676c6791926239d389e7a51c7d691c-lc.min.js
190 ms
texttransformer.lc-3a8242db13bf5975fec07da220844953-lc.min.js
184 ms
popup.lc-be2d7190376f374cca2e9957a02055d4-lc.min.js
177 ms
pril.de 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
Links do not have a discernible name
pril.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
pril.de 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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pril.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Pril.de 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.
pril.de
Open Graph data is detected on the main page of Pril. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: