Your Website Score is

refstore.de

Similar Ranking

26
423 LOCKED
vorsorge.wiki
26
THE-EVIL-NEWS.INFO DISCLAIMER
the-evil-news.info
26
DETLEF FUNDER ART
parallelworld.eu
26
HANDARBEITSGESCHÄFT | SIMPLY STITCH-WOLLE, STOFFE, KURZWAREN
simplystitch.de
26
MESSAGE.WS – PRESSEMELDUNGEN
message.ws
26
GEILE PFLAUME EROTIKMAGAZIN | GEILEPFLAUME.COM
geilepflaume.com
26
HERZLICH WILLKOMMEN AUF RECASTGAMING.DE
recastgaming.de

Latest Sites

34
MONSTERZEUG - SCHENKEN MACHT GLÜCKLICH
monsterzeug.de
40
DAS SURFCAMP VERZEICHNIS - 600 SURFCAMPS ÜBERSICHTLICH SORTIERT!
surfcamp-online.com
19
WILLKOMMEN • WERBUNG.COM
werbung.com
49
SNSMI - TRAVEL INFORMATION
sinisamihajlovic.com
48
IF - TECHNOLOGY NEWS
ihasafunny.com
3
WWW.KARDIOLOGIE-WEIDEN.COM
kardiologie-weiden.de
19
DIGITALE PRODUKTE KATALOG
digitale-produkte-katalog.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

26 mazelle.de Last Updated: 3 weeks

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

Desktop

Mobile

Performance Desktop Score 100%
Best Practices Desktop Score 96%
SEO Desktop Score 50%
Performance Mobile Score 99%
Best Practices Mobile Score 96%
SEO Mobile Score 50%
Page Authority Authority 7%
Domain Authority Domain Authority 6%
Moz Rank 0.7/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 25 Characters
GEPLANTE WARTUNGSAUFGABEN
Meta Description 0 Characters
NO DATA
Effective URL 22 Characters
https://www.mazelle.de
Excerpt Page content
Geplante Wartungsaufgaben Auf der Website werden geplante Wartungsaufgaben durchgeführt. Bitte entschuldigen Sie die Unannehmlichkeiten. Kommen Sie später wieder vorbei. Wir sind bald wieder online. ...
Keywords Cloud Density
wieder2 website1 später1 technologie1 online1 bald1 sind1 vorbei1 kommen1 werden1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
wieder 2
website 1
später 1
technologie 1
online 1
bald 1
sind 1
vorbei 1
kommen 1
werden 1
Google Preview Your look like this in google search result
GEPLANTE WARTUNGSAUFGABEN
https://www.mazelle.de
Geplante Wartungsaufgaben Auf der Website werden geplante Wartungsaufgaben durchgeführt. Bitte entschuldigen Sie die Unannehmlichkeiten. Kommen Sie später wieder vorbei. Wir sind bald wieder online. ...
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~1.79 KB
Code Size: ~1.21 KB
Text Size: ~593 B Ratio: 32.28%

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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoids enormous network payloads Total size was 2,552 KiB
Large network payloads cost users real money and are highly correlated with long load times
Font display Est savings of 120 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
Minimizes main-thread work 0.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Eliminate render-blocking resources Est savings of 120 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Time to Interactive 0.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 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
Serve static assets with an efficient cache policy 2 resources found
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short Root document took 40 ms
Keep the server response time for the main document short because all other requests depend on it
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Render blocking requests Est savings of 140 ms
Requests are blocking the page's initial render, which may delay LCP
Page has unsuccessful HTTP status code 503
Pages with unsuccessful HTTP status codes may not be indexed properly
Largest Contentful Paint element 440 ms
This is the largest contentful element painted within the viewport
Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint 0.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids an excessive DOM size 13 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)
First Contentful Paint 0.3 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid large layout shifts 1 layout shift 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)
Use efficient cache lifetimes Est savings of 3 KiB
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests 2 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 0 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

Mobile

Mobile Screenshot
Server Backend Latencies 0 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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Use efficient cache lifetimes Est savings of 3 KiB
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint 1.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Minimizes main-thread work 0.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Serve static assets with an efficient cache policy 2 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Cumulative Layout Shift 0.003
Cumulative Layout Shift measures the movement of visible elements within the viewport
Eliminate render-blocking resources Est savings of 450 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid chaining critical requests 2 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
Avoids an excessive DOM size 13 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)
Largest Contentful Paint element 1,800 ms
This is the largest contentful element painted within the viewport
Document uses legible font sizes 100% 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
Render blocking requests Est savings of 470 ms
Requests are blocking the page's initial render, which may delay LCP
Avoid large layout shifts 1 layout shift 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)
Initial server response time was short Root document took 40 ms
Keep the server response time for the main document short because all other requests depend on it
Font display Est savings of 80 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
Network Round Trip Times 0 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
Avoids enormous network payloads Total size was 2,552 KiB
Large network payloads cost users real money and are highly correlated with long load times
Time to Interactive 1.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Page has unsuccessful HTTP status code 503
Pages with unsuccessful HTTP status codes may not be indexed properly

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
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not 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
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

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/1.1 503 Service Unavailable
Server: nginx
Date: Wed, 27 Aug 2025 23:36:23 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
X-Powered-By: PHP/8.4.11
Retry-After: 600
Content-Security-Policy: upgrade-insecure-requests
Permissions-Policy: geolocation=(), midi=(),sync-xhr=(),accelerometer=(), gyroscope=(), magnetometer=(), camera=(), fullscreen=(self)
Vary: User-Agent
Referrer-Policy: strict-origin-when-cross-origin
X-Frame-Options: sameorigin
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Strict-Transport-Security: max-age=15768000; includeSubDomains
DNS Records DNS Resource Records associated with a hostname
View DNS Records