5.7 sec in total
437 ms
4.5 sec
738 ms
Welcome to esoterik-punkt.ch homepage info - get ready to check Esoterik Punkt best content right away, or after learning these important things about esoterik-punkt.ch
Esoterik Onlineshop mit Showroom
Visit esoterik-punkt.chWe analyzed Esoterik-punkt.ch page load time and found that the first response time was 437 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
esoterik-punkt.ch performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value8.3 s
2/100
25%
Value6.4 s
41/100
10%
Value110 ms
97/100
30%
Value0.396
25/100
15%
Value8.9 s
34/100
10%
437 ms
107 ms
20 ms
58 ms
9 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Esoterik-punkt.ch, 53% (81 requests) were made to Image.jimcdn.com and 14% (21 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Image.jimcdn.com.
Page size can be reduced by 1.1 MB (3%)
32.1 MB
31.0 MB
In fact, the total size of Esoterik-punkt.ch main page is 32.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. Only a small number of websites need less resources to load. Images take 30.4 MB which makes up the majority of the site volume.
Potential reduce by 132.4 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 26.0 kB, which is 16% 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 132.4 kB or 82% of the original size.
Potential reduce by 3.2 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. Esoterik Punkt images are well optimized though.
Potential reduce by 758.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 758.2 kB or 65% of the original size.
Potential reduce by 210.5 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. Esoterik-punkt.ch needs all CSS files to be minified and compressed as it can save up to 210.5 kB or 71% of the original size.
Number of requests can be reduced by 38 (27%)
142
104
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Esoterik Punkt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.esoterik-punkt.ch
437 ms
layout.css
107 ms
ownbgr.css.64a8890424c831809fe2076b99a6edaa.css
20 ms
web.js.81df69f80213857d0c7a.js
58 ms
27730-212148-12439-26
9 ms
css
54 ms
css
66 ms
st.js
146 ms
image.jpg
257 ms
ga.js
234 ms
analytics.js
234 ms
pdf.png
121 ms
image.jpg
213 ms
image.jpg
214 ms
image.jpg
213 ms
image.jpg
214 ms
image.jpg
502 ms
image.jpg
230 ms
image.jpg
425 ms
image.jpg
443 ms
image.jpg
508 ms
image.jpg
337 ms
image.jpg
443 ms
image.jpg
440 ms
image.jpg
587 ms
image.jpg
644 ms
image.jpg
502 ms
image.jpg
590 ms
image.jpg
787 ms
image.jpg
637 ms
image.jpg
588 ms
image.jpg
790 ms
image.jpg
792 ms
image.jpg
638 ms
image.jpg
793 ms
image.jpg
794 ms
image.jpg
785 ms
image.jpg
941 ms
image.jpg
1018 ms
image.jpg
891 ms
image.jpg
1105 ms
image.jpg
1295 ms
image.jpg
887 ms
image.jpg
970 ms
image.jpg
892 ms
image.jpg
1005 ms
image.jpg
971 ms
f6ETJtZ3CUmBRLiPKYV3VQ.ttf
116 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
117 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
219 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
218 ms
web_unresponsive.css.971844ad255ad24c3140ee452a28b763.css
67 ms
jV7cVMrJnsu-XxUY7LHL.json
181 ms
image.jpg
770 ms
image.jpg
1047 ms
image.jpg
914 ms
image.jpg
792 ms
image.jpg
1027 ms
image.jpg
809 ms
ea80ec5a2c965c54340a933005e22d9d.woff
103 ms
js
107 ms
all.js
313 ms
931bdb6b50816b03206c66921760b246.gif
91 ms
new_embed-d6004936e85bea3a6779a7de0ff4f850.css
85 ms
en-us.js
98 ms
image.jpg
1542 ms
__utm.gif
56 ms
__utm.gif
80 ms
__utm.gif
81 ms
collect
85 ms
image.jpg
774 ms
image.jpg
697 ms
image.jpg
1055 ms
image.jpg
849 ms
common.js
26 ms
map.js
23 ms
util.js
24 ms
marker.js
24 ms
geocoder.js
25 ms
geometry.js
23 ms
directions.js
95 ms
poly.js
97 ms
image.jpg
993 ms
image.jpg
1366 ms
image.jpg
1009 ms
onion.js
31 ms
openhand_8_8.cur
65 ms
StaticMapService.GetMapImage
202 ms
image.jpg
889 ms
image.jpg
1134 ms
image.jpg
1216 ms
ViewportInfoService.GetViewportInfo
51 ms
stats.js
45 ms
controls.js
43 ms
infowindow.js
38 ms
css
149 ms
image.jpg
1175 ms
image.jpg
1078 ms
image.jpg
1274 ms
transparent.png
91 ms
image.jpg
1223 ms
image.jpg
1236 ms
image.jpg
1109 ms
image.jpg
1177 ms
image.jpg
1361 ms
spotlight-poi.png
67 ms
174 ms
image.jpg
1028 ms
google4.png
39 ms
mapcnt6.png
40 ms
sv5.png
40 ms
image.jpg
1376 ms
image.jpg
1394 ms
image.jpg
1253 ms
vt
63 ms
vt
88 ms
xd_arbiter.php
230 ms
xd_arbiter.php
437 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
19 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
19 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
44 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
43 ms
vt
81 ms
vt
80 ms
vt
79 ms
tmapctrl.png
43 ms
tmapctrl4.png
44 ms
imgs8.png
43 ms
image.jpg
1397 ms
image.jpg
1077 ms
image.jpg
1173 ms
image.jpg
1326 ms
image.jpg
1508 ms
AuthenticationService.Authenticate
171 ms
image.jpg
1297 ms
image.jpg
1578 ms
image.jpg
1340 ms
image.jpg
1221 ms
image.jpg
1515 ms
image.jpg
1724 ms
image.jpg
1232 ms
image.jpg
1134 ms
image.jpg
1141 ms
image.jpg
1184 ms
image.jpg
1216 ms
collect
86 ms
loginstate
215 ms
cc.js
86 ms
ping
66 ms
like.php
101 ms
qeKvIRsJabD.js
494 ms
LVx-xkvaJ0b.png
553 ms
esoterik-punkt.ch 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
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.
esoterik-punkt.ch 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
Page has valid source maps
esoterik-punkt.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Esoterik-punkt.ch 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 Esoterik-punkt.ch 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.
esoterik-punkt.ch
Open Graph description is not detected on the main page of Esoterik Punkt. 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: