Your Website Score is

Similar Ranking

31
GESCHICHTE ABITURVORBEREITUNG 2023 - GESCHICHTE KOMPAKT
geschichte-abitur.de
31
STARTSEITE - PFLEGE MIT HERZ - MARKKLEEBERG
pmh-markkleeberg.de
31
MIETWERKSTATT-PORTAL - MIETWERKSTATT IN DEINER NÄHE FINDEN
mietwerkstatt-portal.de
31
UG300 LINK ALTERNATIF|SLOT BONUS|NEW MEMBER 100% DIAWAL
ug300.fun
31
QR CODE GENERATOR MIT LOGO - WHATSAPP, WIFI, BITCOIN, STANDORT, SMS SOWIE TEXT
qr-code-erstellen.com
31
MARKTPLATZ MITTELSTAND - DAS ONLINE-MARKETING-NETZWERK FÜR KMUS, SELBSTSTÄNDIGE UND FREIBERUFLER
marktplatz-mittelstand.de
31
SOTECON • IT-SYSTEMHAUS
sotecon.de

Latest Sites

21
LEARN SPANISH GRAMMAR - SPANISH GRAMMAR LESSONS
spanishgrammarlessons.com
26
MESSAGE.WS – PRESSEMELDUNGEN
message.ws
19
TÜBINGEN - TAXISTA
taxista.de
6
RATGEBER MIT FRAGEN UND ANTWORTEN ZU VIELEN THEMEN
www.meinefragen.net
22
REISESUCHMASCHINE TRAVEL-LIST.DE | REISE PREISVERGLEICH VON LASTMINUTE REISE, KREUZFAHRT, FERIENHAUS UND FERIENWOHNUNGEN
www.travel-list.de
27
КАТАЛОГ ЗАПЧАСТЕЙ НА ИНОМАРКИ - НА ВАРШАВКЕ
autoparts.v45.ru
14
СТУДИЯ ЦВЕТОЧНОГО ДИЗАЙНА - ОФОРМЛЕНИЕ СВАДЕБ ЦВЕТАМИ, СВАДЕБНЫЙ БУКЕТ НЕВЕСТЫ, СВАДЕБНАЯ ФЛОРИСТИКА, НОВОГОДНИЕ УКРАШЕНИЕ ПОМЕЩЕНИЙ ЮЗАО МОСКВА
creativebouquet.ru

Top Technologies

PHP
Programming Languages
Apache
Web Servers
WordPress
CMS
Google Font API
Font Scripts
jQuery
JavaScript Frameworks
Nginx
Web Servers
Font Awesome
Font Scripts
Yoast SEO
SEO
Google AdSense
Advertising Networks
CloudFlare
CDN

31 pmh-markkleeberg.de Last Updated: 2 weeks

Success 62% of passed verification steps
Warning 23% of total warning
Errors 15% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 55%
Best Practices Desktop Score 78%
SEO Desktop Score 92%
PWA Desktop Score 29%
Performance Mobile Score 48%
Best Practices Mobile Score 78%
SEO Mobile Score 93%
PWA Mobile Score 38%
Page Authority Authority 12%
Domain Authority Domain Authority 6%
Moz Rank 1.2/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 43 Characters
STARTSEITE - PFLEGE MIT HERZ - MARKKLEEBERG
Meta Description 88 Characters
Willkommen auf der Startseite des ambulanten Pflegedienstes "Pflege mit Herz".
Effective URL 27 Characters
https://pmh-markkleeberg.de
Excerpt Page content
Startseite - Pflege mit Herz - Markkleeberg Startseite Über Uns Neuigkeiten News Veranstaltung Kontakt ...
Keywords Cloud Density
pflege11 herz10 ihnen7 pflegedienst6 unserer5 unsere5 auch5 stehen5 team5 dörling4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
pflege 11
herz 10
ihnen 7
pflegedienst 6
unserer 5
unsere 5
auch 5
stehen 5
team 5
dörling 4
Google Preview Your look like this in google search result
STARTSEITE - PFLEGE MIT HERZ - MARKKLEEBERG
https://pmh-markkleeberg.de
Willkommen auf der Startseite des ambulanten Pflegedienstes "Pflege mit Herz".
Robots.txt File Detected
http://pmh-markkleeberg.de/robots.txt
Sitemap.xml File Detected
http://pmh-markkleeberg.de/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~169.91 KB
Code Size: ~27.06 KB
Text Size: ~142.84 KB Ratio: 84.07%

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
Does not use HTTPS 1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Serve images in next-gen formats Potential savings of 1,163 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids an excessive DOM size 302 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)
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
Largest Contentful Paint 4.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid chaining critical requests 27 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
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minify JavaScript Potential savings of 100 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Time to Interactive 1.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Properly size images Potential savings of 346 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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 initial server response time Root document took 3,190 ms
Keep the server response time for the main document short because all other requests depend on it
Cumulative Layout Shift 0.249
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid non-composited animations 8 animated elements found
Animations which are not composited can be janky and increase CLS
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 CSS Potential savings of 46 KiB
Minifying CSS files can reduce network payload sizes
Minimize third-party usage Third-party code blocked the main thread for 0 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
Minimizes main-thread work 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 3 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)
Reduce unused JavaScript Potential savings of 577 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Reduce unused CSS Potential savings of 554 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Efficiently encode images Potential savings of 16 KiB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 1,085 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Eliminate render-blocking resources Potential savings of 370 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid large layout shifts 15 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)
Serve static assets with an efficient cache policy 38 resources found
A long cache lifetime can speed up repeat visits to your page
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Largest Contentful Paint element 4,510 ms
This is the largest contentful element painted within the viewport
Speed Index 4.1 s
Speed Index shows how quickly the contents of a page are visibly populated
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid enormous network payloads Total size was 4,319 KiB
Large network payloads cost users real money and are highly correlated with long load times

Mobile

Mobile Screenshot
Reduce initial server response time Root document took 2,120 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce unused JavaScript Potential savings of 577 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Serve static assets with an efficient cache policy 38 resources found
A long cache lifetime can speed up repeat visits to your page
Minify JavaScript Potential savings of 100 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Max Potential First Input Delay 200 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid non-composited animations 4 animated elements found
Animations which are not composited can be janky and increase CLS
Cumulative Layout Shift 0.185
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Contentful Paint 4.1 s
First Contentful Paint marks the time at which the first text or image is painted
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
Enable text compression Potential savings of 1,085 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Reduce unused CSS Potential savings of 552 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
First Meaningful Paint 4.1 s
First Meaningful Paint measures when the primary content of a page is visible
Reduce JavaScript execution time 1.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 15 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)
Avoids an excessive DOM size 302 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)
Avoid long main-thread tasks 13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Reduce the impact of third-party code Third-party code blocked the main thread for 300 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
Defer offscreen images Potential savings of 1,083 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Document uses legible font sizes 99.91% 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
Avoid large layout shifts 2 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)
Efficiently encode images Potential savings of 23 KiB
Optimized images load faster and consume less cellular data
Avoid chaining critical requests 27 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
Server Backend Latencies 170 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
Properly size images Potential savings of 171 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Time to Interactive 18.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Total Blocking Time 360 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve images in next-gen formats Potential savings of 1,082 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Tap targets are sized appropriately 100% 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 11.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 4,900 ms
This is the largest contentful element painted within the viewport
Avoid enormous network payloads Total size was 4,174 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint 4.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 1,940 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minify CSS Potential savings of 46 KiB
Minifying CSS files can reduce network payload sizes
Minimize main-thread work 3.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Does not use HTTPS 1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

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
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links
First 14 Links Relationship HTTP Status
https://pmh-markkleeberg.de/ Internal Link 200
Startseite Internal Link 200
Über Uns Internal Link 200
Neuigkeiten Internal Link 200
News Internal Link 200
Veranstaltung Internal Link 200
Kontakt Internal Link 200
Angebote Internal Link 200
Karriere Internal Link 200
Jobs Internal Link 301
Was wir leisten Internal Link 301
Impressum Internal Link 200
Datenschutz Internal Link 200
RSS Internal Link 200

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 
date: Thu, 18 Apr 2024 16:39:52 GMT
server: Apache/2.4.59 (Unix)
x-powered-by: PHP/8.3.6
link: ; rel="https://api.w.org/"
link: ; rel="alternate"; type="application/json"
link: ; rel=shortlink
vary: User-Agent
content-type: text/html; charset=UTF-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A pmh-markkleeberg.de 81.169.145.150 IN 29
NS pmh-markkleeberg.de shades05.rzone.de IN 150
NS pmh-markkleeberg.de docks11.rzone.de IN 150
MX pmh-markkleeberg.de smtpin.rzone.de IN 150
AAAA pmh-markkleeberg.de 2a01:238:20a:202:1150:: IN 29

About Us

Contact Info

Follow Us

Copyright 2021 - 2023 Webseitenwert.de - Alle Rechte vorbehalten | Impressum | Datenschutz | Imprint | Data Protection | Cookie-Einstellungen
Languages | English