3.1 sec in total
699 ms
2 sec
398 ms
Welcome to pulsar.li homepage info - get ready to check Pulsar best content for Germany right away, or after learning these important things about pulsar.li
Alles für kolloidales Silberwasser und Goldwasser, Elektroden, Silberwassergeräte, Informationsmedizin
Visit pulsar.liWe analyzed Pulsar.li page load time and found that the first response time was 699 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
pulsar.li performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value6.4 s
10/100
25%
Value8.4 s
19/100
10%
Value9,150 ms
0/100
30%
Value0.018
100/100
15%
Value16.7 s
5/100
10%
699 ms
195 ms
195 ms
196 ms
69 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 56% of them (41 requests) were addressed to the original Pulsar.li, 18% (13 requests) were made to Apis.google.com and 3% (2 requests) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Pulsar.li.
Page size can be reduced by 661.9 kB (66%)
998.0 kB
336.1 kB
In fact, the total size of Pulsar.li main page is 998.0 kB. 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. Javascripts take 638.4 kB which makes up the majority of the site volume.
Potential reduce by 52.2 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 52.2 kB or 73% of the original size.
Potential reduce by 1.4 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. Pulsar images are well optimized though.
Potential reduce by 402.6 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 402.6 kB or 63% of the original size.
Potential reduce by 205.7 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. Pulsar.li needs all CSS files to be minified and compressed as it can save up to 205.7 kB or 83% of the original size.
Number of requests can be reduced by 35 (49%)
72
37
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pulsar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
pulsar.li
699 ms
s.css
195 ms
ssb.css
195 ms
shp.css
196 ms
plusone.js
69 ms
addthis_widget.js
36 ms
widgets.js
35 ms
ga.js
28 ms
2374_SA_TARGET_120x60.gif
204 ms
pll.gif
182 ms
s2dlogo.gif
1444 ms
pln700.gif
202 ms
pbmts.gif
402 ms
ptd.gif
401 ms
pbmtm1.gif
402 ms
pbmtm2.gif
401 ms
pbmtm3.gif
401 ms
pbmtm4.gif
474 ms
pbmtm5.gif
473 ms
pbmtm6.gif
475 ms
pbmtm7.gif
470 ms
pcp.gif
468 ms
pnavmemo.gif
656 ms
pnavshowbasket.gif
655 ms
pnavcheckout.gif
655 ms
ph00000000000000001.gif
685 ms
pbigt.gif
654 ms
pulsartext052015_366.gif
828 ms
pbigb.gif
828 ms
psidt.gif
828 ms
colloidalsilver_146.jpg
859 ms
psidb.gif
830 ms
pulsarmagazin200_146.gif
857 ms
pulsarnr1cols2.gif
857 ms
paypallogocols2.gif
857 ms
ytcolloiddevicemini_366.jpg
851 ms
aidsverbrechen_146.gif
945 ms
grippe_146.jpg
1040 ms
wantedhugostamm_146.gif
1137 ms
pcd.gif
946 ms
neuershopbesserepreise150x165_sbp.gif
947 ms
pulsarmagazin200_sbp.gif
1041 ms
cb=gapi.loaded_0
106 ms
cm
372 ms
__utm.gif
94 ms
pbigl.gif
951 ms
pbigr.gif
952 ms
cb=gapi.loaded_1
43 ms
cb=gapi.loaded_2
41 ms
badge
230 ms
badge
283 ms
psidl.gif
977 ms
psidr.gif
958 ms
uvbK9RxORKQ
271 ms
postmessageRelay
306 ms
rs=AGLTcCMwT-oO1EOUpPJIUTzRq-IrQ9C8Bw
37 ms
rs=AGLTcCP1XWuWX_iCC9WgWr0vKsRUFWxeag
79 ms
rs=AGLTcCO4_kUmmqUKcIUh5gu2XNIdwNS-hg
126 ms
photo.jpg
260 ms
gplus-dd4b38-20.png
226 ms
41-6JqH6YPL._SL110_.jpg
199 ms
360 ms
www-embed-player-vflfNyN_r.css
242 ms
www-embed-player.js
309 ms
buy-from-tan.gif
192 ms
rs=AGLTcCO4_kUmmqUKcIUh5gu2XNIdwNS-hg
76 ms
10_en_btn.gif
387 ms
rs=AGLTcCO4_kUmmqUKcIUh5gu2XNIdwNS-hg
59 ms
3193398744-postmessagerelay.js
15 ms
rpc:shindig_random.js
137 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
71 ms
ad_status.js
68 ms
cb=gapi.loaded_0
18 ms
pulsar.li 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
pulsar.li 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
Page has valid source maps
pulsar.li 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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pulsar.li can be misinterpreted by Google and other search engines. Our service has detected that German 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 Pulsar.li 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.
pulsar.li
Open Graph description is not detected on the main page of Pulsar. 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: