Your Website Score is

Similar Ranking

30
LEON SCHMIDT - DEIN ONLINE FITNESS COACH BEI LIEBEISSTLEBEN
liebeisstleben.de
30
SHOP FÜR PC KAUFEN, GAMING PC, LAPTOP KAUFEN & WORKSTATIONS | CLS
cls-computer.de
30
THE PAGE IS TEMPORARILY UNAVAILABLE
gimp-handbuch.de
30
FOODTROTTER - FOODTROTTER
foodtrotter.com
30
ÇAKIRLAR SAĞLIK KABINI - BATIKENT ANKARA
cakirlarsaglikkabini.com.tr
30
DIE GESUNDE WAHRHEIT - MEHR GESUNDHEIT MIT MUTTER NATUR
die-gesunde-wahrheit.de
29
❶ SEO ANALYSIS TOOL • FREE WEBSITE TOOLS • RANK BOOSTER[NEW!]????
directorylib.com

Latest Sites

19
PROGAMERSMART | YOUR ONE-STOP SHOP FOR GAMING GEAR
progamersmart.com
31
STARTSEITE - PFLEGE MIT HERZ - MARKKLEEBERG
pmh-markkleeberg.de
24
VON DER MASCHINE ZUR REALITÄT, WIE DIE BLAUEN POKIES ECHTE PERSÖNLICHKEITEN WERDEN
paranormal-pictures.de
2
ACHTZIGER-FORUM - PORTAL
achtziger-forum.de
26
- WEIHNACHTSKARTENSPRUECHEWEIHNACHTSKARTENSPRUECHE | STIMMUNGSVOLLE SPRÜCHE FÜR KARTEN UND SCRAP BOOKS
weihnachtskartensprueche.de
31
MARKTPLATZ MITTELSTAND - DAS ONLINE-MARKETING-NETZWERK FÜR KMUS, SELBSTSTÄNDIGE UND FREIBERUFLER
marktplatz-mittelstand.de

Top Technologies

Apache
Web Servers
WordPress
CMS
Google Font API
Font Scripts
Nginx
Web Servers
Font Awesome
Font Scripts
Yoast SEO
SEO
Google AdSense
Advertising Networks
Twitter Bootstrap
Web Frameworks

30 die-gesunde-wahrheit.de Last Updated: 2 days

Success 78% of passed verification steps
Warning 7% of total warning
Errors 15% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 56%
Best Practices Desktop Score 74%
SEO Desktop Score 92%
PWA Desktop Score 29%
Performance Mobile Score 29%
Best Practices Mobile Score 70%
SEO Mobile Score 91%
PWA Mobile Score 38%
Page Authority Authority 37%
Domain Authority Domain Authority 33%
Moz Rank 3.7/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 55 Characters
DIE GESUNDE WAHRHEIT - MEHR GESUNDHEIT MIT MUTTER NATUR
Meta Description 32 Characters
Mehr Gesundheit mit Mutter Natur
Effective URL 31 Characters
https://die-gesunde-wahrheit.de
Excerpt Page content
Die gesunde Wahrheit - Mehr Gesundheit mit Mutter Natur Skip to content News Psychologie Home Gesundheit Ernährung Hausmittel Lifes...
Keywords Cloud Density
cookies19 website11 hausmittel11 gegen10 diese9 natürliche9 vorteile8 april8 visitors5 harnsäurewerte5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
cookies 19
website 11
hausmittel 11
gegen 10
diese 9
natürliche 9
vorteile 8
april 8
visitors 5
harnsäurewerte 5
Google Preview Your look like this in google search result
DIE GESUNDE WAHRHEIT - MEHR GESUNDHEIT MIT MUTTER NATUR
https://die-gesunde-wahrheit.de
Mehr Gesundheit mit Mutter Natur
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~73.81 KB
Code Size: ~48.39 KB
Text Size: ~25.42 KB Ratio: 34.44%

Estimation Traffic and Earnings

0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Avoid non-composited animations 7 animated elements found
Animations which are not composited can be janky and increase CLS
Avoid long main-thread tasks 14 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid enormous network payloads Total size was 2,993 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid large layout shifts 2 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint element 2,470 ms
This is the largest contentful element painted within the viewport
Total Blocking Time 400 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Eliminate render-blocking resources Potential savings of 420 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint 2.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Max Potential First Input Delay 180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Server Backend Latencies 260 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Reduce unused CSS Potential savings of 47 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid an excessive DOM size 905 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Serve images in next-gen formats Potential savings of 211 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid large layout shifts 9 elements found
These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Serve static assets with an efficient cache policy 19 resources found
A long cache lifetime can speed up repeat visits to your page
User Timing marks and measures 15 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Defer offscreen images Potential savings of 33 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 36 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Minify JavaScript Potential savings of 117 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Cumulative Layout Shift 0.163
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Network Round Trip Times 30 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Reduce unused JavaScript Potential savings of 963 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid chaining critical requests 22 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Reduce JavaScript execution time 2.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 4.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Minimize third-party usage Third-party code blocked the main thread for 150 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Minimize main-thread work 5.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short Root document took 110 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid serving legacy JavaScript to modern browsers Potential savings of 80 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser

Mobile

Mobile Screenshot
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Defer offscreen images Potential savings of 363 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Total Blocking Time 1,840 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid large layout shifts 7 elements found
These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Network Round Trip Times 30 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Avoid large layout shifts 4 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
User Timing marks and measures 15 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Time to Interactive 17.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoid an excessive DOM size 900 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Reduce the impact of third-party code Third-party code blocked the main thread for 1,030 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Avoid enormous network payloads Total size was 2,810 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid serving legacy JavaScript to modern browsers Potential savings of 80 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Max Potential First Input Delay 450 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Server Backend Latencies 260 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Minify JavaScript Potential savings of 117 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Reduce unused JavaScript Potential savings of 916 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Reduce JavaScript execution time 5.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce unused CSS Potential savings of 32 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Largest Contentful Paint 4.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Cumulative Layout Shift 0.295
Cumulative Layout Shift measures the movement of visible elements within the viewport
Serve images in next-gen formats Potential savings of 200 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
First Meaningful Paint 4.3 s
First Meaningful Paint measures when the primary content of a page is visible
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes
Largest Contentful Paint element 4,820 ms
This is the largest contentful element painted within the viewport
Initial server response time was short Root document took 270 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid chaining critical requests 28 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Serve static assets with an efficient cache policy 19 resources found
A long cache lifetime can speed up repeat visits to your page
Minimize main-thread work 11.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Tap targets are not sized appropriately 88% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements
Speed Index 9.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid non-composited animations 7 animated elements found
Animations which are not composited can be janky and increase CLS
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources Potential savings of 290 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Properly size images Potential savings of 49 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Document uses legible font sizes 99.96% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
server: nginx
date: Wed, 17 Apr 2024 13:01:26 GMT
content-type: text/html; charset=UTF-8
content-length: 15271
vary: User-Agent,Accept-Encoding
last-modified: Wed, 17 Apr 2024 05:17:51 GMT
accept-ranges: bytes
content-encoding: gzip
cache-control: max-age=0, no-cache, no-store, must-revalidate
pragma: no-cache
expires: Mon, 29 Oct 1923 20:30:00 GMT
DNS Records DNS Resource Records associated with a hostname
View DNS Records