5.9 sec in total
1.2 sec
4.1 sec
614 ms
Visit incantator.de now to see the best up-to-date Incantator content for Germany and also check out these interesting facts you probably never knew about incantator.de
This domain may be for sale!
Visit incantator.deWe analyzed Incantator.de page load time and found that the first response time was 1.2 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
incantator.de performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value1.4 s
100/100
25%
Value1.2 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.9 s
100/100
10%
1209 ms
190 ms
205 ms
486 ms
293 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 39% of them (34 requests) were addressed to the original Incantator.de, 17% (15 requests) were made to Dmp.theadex.com and 10% (9 requests) were made to Ih.adscale.de. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Incantator.de.
Page size can be reduced by 422.2 kB (27%)
1.5 MB
1.1 MB
In fact, the total size of Incantator.de main page is 1.5 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. 35% of websites need less resources to load. Images take 930.9 kB which makes up the majority of the site volume.
Potential reduce by 62.0 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 62.0 kB or 81% of the original size.
Potential reduce by 40.9 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. Incantator images are well optimized though.
Potential reduce by 309.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 309.3 kB or 59% of the original size.
Potential reduce by 9.9 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. Incantator.de needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 83% of the original size.
Number of requests can be reduced by 52 (67%)
78
26
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Incantator. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and as a result speed up the page load time.
www.incantator.de
1209 ms
style.css
190 ms
pagenavi-css.css
205 ms
jquery.js
486 ms
jquery-migrate.min.js
293 ms
praeludium_testroom.js
305 ms
prototype.js
475 ms
adsbygoogle.js
17 ms
wp-emoji-release.min.js
100 ms
ga.js
7 ms
adex.js
265 ms
rc
221 ms
__utm.gif
11 ms
body_bg.gif
138 ms
spacer.gif
137 ms
schuppenflechte.jpg
469 ms
thinkstockphotos_179103931-e1448619847781.jpg
193 ms
Gruenes-Gemuese.jpg
1027 ms
rueckenschmerzen.jpg
467 ms
haut-rot.jpg
1076 ms
go.gif
197 ms
ca-pub-3081753574191471.js
166 ms
zrt_lookup.html
62 ms
show_ads_impl.js
70 ms
header1.jpg
365 ms
header2.jpg
507 ms
bbg.gif
462 ms
date-bg.gif
541 ms
_bookmark.php
665 ms
_bookmark.php
677 ms
_bookmark.php
720 ms
_bookmark.php
742 ms
_bookmark.php
876 ms
call.sjs
102 ms
ads
30 ms
osd.js
32 ms
Rest;sz=120x600,160x600,200x600,300x600;;tile=1;prae=y;flash=no;adset=f;ord=200507238074
295 ms
Cookie
103 ms
t.js
88 ms
1.gif
89 ms
analytic.js
170 ms
173 ms
getads.js
11 ms
t.js
90 ms
pixel
19 ms
redirect
278 ms
cm.gif
86 ms
impr
102 ms
2.gif
86 ms
wong.gif
111 ms
blinklist.gif
160 ms
webnews.gif
181 ms
delicious.gif
206 ms
yigg.gif
258 ms
google.gif
274 ms
yahoo.gif
302 ms
adex.js
85 ms
rtb
134 ms
redirect
361 ms
1.gif
94 ms
analytic.js
94 ms
88 ms
match
87 ms
adition.js
358 ms
js
283 ms
2.gif
89 ms
loadImages.js
3 ms
0
86 ms
nuggad
110 ms
2.gif
87 ms
banner
177 ms
uid.html
89 ms
callback.js
4 ms
impr
91 ms
111
148 ms
adex.js
169 ms
mtrcs_284704.js
286 ms
head_bg1.jpg
101 ms
spacer.gif
99 ms
search_bg.jpg
254 ms
2.gif
86 ms
match
8 ms
mtrcs_284704.js
9 ms
pql
18 ms
gw.js
21 ms
650
101 ms
Cookie
103 ms
42036394.js
19 ms
incantator.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
Form elements do not have associated labels
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.
incantator.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
incantator.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
Tap targets are not sized appropriately
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Incantator.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 Incantator.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.
incantator.de
Open Graph description is not detected on the main page of Incantator. 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: