6.9 sec in total
237 ms
6.4 sec
247 ms
Welcome to mystische-orte.de homepage info - get ready to check Mystische Orte best content for Germany right away, or after learning these important things about mystische-orte.de
Visit mystische-orte.deWe analyzed Mystische-orte.de page load time and found that the first response time was 237 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mystische-orte.de performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value12.3 s
0/100
25%
Value13.7 s
2/100
10%
Value3,630 ms
1/100
30%
Value0.058
98/100
15%
Value29.6 s
0/100
10%
237 ms
532 ms
94 ms
190 ms
379 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mystische-orte.de, 5% (8 requests) were made to Cdn.regiondo.net and 1% (2 requests) were made to Widgets.regiondo.net. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Stadtspuerer.de.
Page size can be reduced by 459.1 kB (19%)
2.4 MB
2.0 MB
In fact, the total size of Mystische-orte.de main page is 2.4 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. 70% of websites need less resources to load. Images take 909.2 kB which makes up the majority of the site volume.
Potential reduce by 106.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. 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 106.5 kB or 79% of the original size.
Potential reduce by 12.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. Mystische Orte images are well optimized though.
Potential reduce by 155.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 155.6 kB or 25% of the original size.
Potential reduce by 184.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. Mystische-orte.de needs all CSS files to be minified and compressed as it can save up to 184.7 kB or 25% of the original size.
Number of requests can be reduced by 136 (93%)
146
10
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mystische Orte. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 85 to 1 for JavaScripts and from 53 to 1 for CSS and as a result speed up the page load time.
stadtspuerer.de
237 ms
www.stadtspuerer.de
532 ms
icons-map.min.css
94 ms
bb-icons.min.css
190 ms
dashicons.min.css
379 ms
buddypress.min.css
571 ms
bdt-uikit.css
398 ms
ep-helper.css
306 ms
buddyboss_legacy.css
309 ms
style-buddypanel.css
310 ms
index.min.css
403 ms
bb-access-control.min.css
403 ms
bb-tutorlms-admin.min.css
405 ms
mentions.min.css
470 ms
woocommerce-layout.css
491 ms
woocommerce.css
494 ms
learndash_quiz_front.min.css
500 ms
styles.css
502 ms
jquery.dropdown.min.css
563 ms
learndash_lesson_video.min.css
601 ms
cookieblocker.min.css
602 ms
extendify-utilities.css
603 ms
fonts.css
606 ms
learndash.min.css
665 ms
elementor-icons.min.css
675 ms
frontend-lite.min.css
679 ms
swiper.min.css
686 ms
post-5.css
688 ms
frontend-lite.min.css
689 ms
global.css
757 ms
post-6.css
760 ms
post-35313.css
771 ms
post-35338.css
772 ms
post-159.css
774 ms
bp-zoom.min.css
870 ms
magnific-popup.min.css
854 ms
select2.min.css
859 ms
regiondo-button.js
22 ms
product-widget.min.js
40 ms
catalog-widget.min.js
42 ms
regiondo-reviews.js
24 ms
theme.min.css
970 ms
template-v2.min.css
791 ms
buddypress.min.css
888 ms
bbpress.min.css
648 ms
learndash.min.css
655 ms
woocommerce.min.css
684 ms
elementor.min.css
622 ms
plugins.min.css
650 ms
custom.css
655 ms
fontawesome.min.css
658 ms
solid.min.css
664 ms
widget-nav-menu.min.css
604 ms
wc-blocks.css
669 ms
ep-font.css
664 ms
ep-navbar.css
662 ms
mailpoet-public.c5d405bf.css
662 ms
twemoji.min.js
604 ms
bb-emoji-loader.min.js
571 ms
jquery.min.js
648 ms
jquery-migrate.min.js
657 ms
bb-reaction.min.js
659 ms
bb-tutorlms-admin.min.js
660 ms
magnific-popup.js
593 ms
widget-members.min.js
593 ms
jquery-query.min.js
658 ms
jquery-cookie.min.js
657 ms
jquery-scroll-to.min.js
656 ms
js.cookie.min.js
660 ms
cart-fragments.min.js
593 ms
jquery.blockUI.min.js
594 ms
add-to-cart.min.js
662 ms
woocommerce.min.js
663 ms
custom.js
664 ms
isInViewport.min.js
638 ms
moment.min.js
638 ms
livestamp.min.js
624 ms
underscore.min.js
716 ms
wp-util.min.js
645 ms
wp-polyfill-inert.min.js
628 ms
regenerator-runtime.min.js
608 ms
wp-polyfill.min.js
609 ms
hooks.min.js
602 ms
i18n.min.js
628 ms
buddypress-nouveau.min.js
626 ms
jquery.guillotine.min.js
619 ms
comment-reply.min.js
616 ms
heartbeat.min.js
611 ms
core.min.js
525 ms
menu.min.js
650 ms
dom-ready.min.js
649 ms
a11y.min.js
650 ms
autocomplete.min.js
649 ms
buddypress-search.min.js
644 ms
buddypress-moderation.min.js
643 ms
draggabilly.min.js
590 ms
bbp-scrubber.min.js
587 ms
jquery.caret.min.js
587 ms
jquery.atwho.min.js
588 ms
mentions.min.js
587 ms
sourcebuster.min.js
588 ms
order-attribution.min.js
562 ms
learndash.js
562 ms
jquery.mask.js
564 ms
bp-zoom.min.js
568 ms
bb-countdown.min.js
569 ms
imagesloaded.min.js
569 ms
masonry.min.js
564 ms
menu.js
526 ms
fitvids.js
508 ms
slick.min.js
516 ms
panelslider.min.js
513 ms
regiondo-button.css
7 ms
sticky-kit.js
509 ms
regiondo-cart-icon.png
93 ms
regiondo-close.png
23 ms
jssocials.min.js
491 ms
main.min.js
492 ms
validate.min.js
493 ms
select2.full.min.js
502 ms
progressbar.min.js
507 ms
mousewheel.min.js
508 ms
learndash.min.js
506 ms
bb-woocommerce.min.js
508 ms
elementor.min.js
508 ms
complianz.min.js
518 ms
public.js
524 ms
jquery.smartmenus.min.js
393 ms
bdt-uikit.min.js
566 ms
webpack.runtime.min.js
481 ms
frontend-modules.min.js
483 ms
waypoints.min.js
482 ms
frontend.min.js
485 ms
%23ecf3f4%2C%23ffffff%2C%233d3d3d%2C%23ecb86b
1940 ms
helper.min.js
454 ms
webpack-pro.runtime.min.js
534 ms
frontend.min.js
537 ms
elements-handlers.min.js
537 ms
adminbar-background.png
562 ms
logo-mystix-motto-geheimnisse-der-stadt-768x271.png
670 ms
element-pack.ttf
641 ms
DS_Gutscheine_Silber-300x140.jpg
621 ms
stadtspuerer_neu_startseite_bild.jpg
1037 ms
www.stadtspuerer.de
2642 ms
jquery-2.2.4.min.js
4 ms
jquery.noconflict.js
3 ms
loader.js
20 ms
reviewwidget.js
22 ms
woocommerce-smallscreen.css
95 ms
mystische-orte.de accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA progressbar elements do not have accessible names.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
mystische-orte.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Missing source maps for large first-party JavaScript
mystische-orte.de SEO score
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mystische-orte.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 Mystische-orte.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.
mystische-orte.de
Open Graph description is not detected on the main page of Mystische Orte. 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: