Your Website Score is

Similar Ranking

18
STARTSEITE | ONMYLIST.DE
onmylist.de
18
503 SERVICE TEMPORARILY UNAVAILABLE
triumph-lifttechnik.de
18
HOME
kaufdown.de
18
KAFFEEVOLLAUTOMATEN MIETEN, LEASEN ODER KAUFEN | CAFFIA LEIPZIG
caffia.de
18
AUTOUNFALL.INFO
autounfall.info
18
WEIHNACHTSDEKOBASTELN
weihnachtsdekobasteln.de
18
NEMESO - NEW MEDIA SOLUTIONS | INTERNET SERVICE PROVIDER BERLIN
nemeso.de

Latest Sites

52
NEW CITIZENS VIABILITY LAW ENFORCEMENT – NEW CITIZENS VIABILITY LAW ENFORCEMENT
ncvle.com
47
CELEBRITIES NEWSS
celebritiesnewss.com
27
BLOG POSTSERVER | VERSANDLÖSUNGEN, TECHNOLOGIE & UNTERNEHMENSWACHSTUM
postserver.at
12
THE PAGE IS TEMPORARILY UNAVAILABLE
gute-reisen-online.com
6
THE PAGE IS TEMPORARILY UNAVAILABLE
papp-paletten.com
36
HOME -
internettv.ch
14
THE-EVIL-NEWS.INFO DISCLAIMER
the-evil-news.info

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

18 onmylist.de Last Updated: 1 day

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

Desktop

Mobile

Performance Desktop Score 89%
Best Practices Desktop Score 96%
SEO Desktop Score 92%
Performance Mobile Score 70%
Best Practices Mobile Score 96%
SEO Mobile Score 92%
Page Authority Authority 7%
Domain Authority Domain Authority 14%
Moz Rank 0.7/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 24 Characters
STARTSEITE | ONMYLIST.DE
Meta Description 0 Characters
NO DATA
Effective URL 23 Characters
https://www.onmylist.de
Google Preview Your look like this in google search result
STARTSEITE | ONMYLIST.DE
https://www.onmylist.de
Robots.txt File Detected
http://onmylist.de/robots.txt
Sitemap.xml File Detected
http://onmylist.de/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~1.91 MB
Code Size: ~197.05 KB
Text Size: ~1.71 MB Ratio: 89.90%

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

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Serve images in next-gen formats Est savings of 246 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Minimizes main-thread work 1.2 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 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)
Eliminate render-blocking resources Est savings of 150 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid an excessive DOM size 1,849 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)
Initial server response time was short Root document took 90 ms
Keep the server response time for the main document short because all other requests depend on it
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
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid long main-thread tasks 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint 1.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Improve image delivery Est savings of 136 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
JavaScript execution time 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Total Blocking Time 220 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoids enormous network payloads Total size was 1,132 KiB
Large network payloads cost users real money and are highly correlated with long load times
Properly size images Est savings of 17 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Max Potential First Input Delay 320 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Avoid chaining critical requests 8 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
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
Legacy JavaScript Est savings of 39 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Reduce unused JavaScript Est savings of 120 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Efficiently encode images Est savings of 22 KiB
Optimized images load faster and consume less cellular data
Time to Interactive 1.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Reduce unused CSS Est savings of 237 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid serving legacy JavaScript to modern browsers Est savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Largest Contentful Paint element 1,060 ms
This is the largest contentful element painted within the viewport

Mobile

Mobile Screenshot
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element 4,210 ms
This is the largest contentful element painted within the viewport
Reduce initial server response time Root document took 3,830 ms
Keep the server response time for the main document short because all other requests depend on it
Properly size images Est savings of 39 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Avoid serving legacy JavaScript to modern browsers Est savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Serve images in next-gen formats Est savings of 144 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid an excessive DOM size 1,849 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)
Improve image delivery Est savings of 124 KiB
Reducing the download time of images can improve the perceived load time of the page and 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)
Reduce unused CSS Est savings of 239 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Legacy JavaScript Est savings of 39 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
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
Reduce unused JavaScript Est savings of 120 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Server Backend Latencies 10 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
Speed Index 9.5 s
Speed Index shows how quickly the contents of a page are visibly populated
JavaScript execution time 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minimizes main-thread work 1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 4.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid chaining critical requests 20 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
Eliminate render-blocking resources Est savings of 920 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Max Potential First Input Delay 320 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids enormous network payloads Total size was 983 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint 3.5 s
First Contentful Paint marks the time at which the first text or image is painted
Total Blocking Time 140 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Time to Interactive 5.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
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
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

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
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
Congratulations! Your website appears to have a favicon.
Broken Links
Warning! You have broken links View links
First 20 Links Relationship HTTP Status
Einloggen Internal Link 200
Kontakt Internal Link 200
Onmylist.de Internal Link 200
Agenturen entdecken Internal Link 200
Webentwicklungs-Agentur Internal Link 0
WordPress-Agentur Internal Link 200
Webflow-Agentur Internal Link 200
Homepage-Agentur Internal Link 200
HTML5-Agenturen Internal Link 200
Joomla-Agenturen Internal Link 0
Agentur für App-Entwicklung Internal Link 200
Agentur für Android-Entwicklung Internal Link 200
Agentur für iOS-Entwicklung Internal Link 200
Mobile-Spiele-Agentur Internal Link 200
jQuery-Mobile-Agentur Internal Link 200
Xcode-Agentur Internal Link 200
Amazon-Full-Service-Agentur Internal Link 301
Amazon-Marketing-Agentur Internal Link 301
Amazon-PPC-Agentur Internal Link 301
Amazon-SEO-Agentur Internal Link 301

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 
vary: User-Agent,Accept-Encoding
last-modified: Mon, 30 Jun 2025 11:04:29 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
content-type: text/html; charset=UTF-8
date: Tue, 01 Jul 2025 04:01:28 GMT
server: Apache
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A onmylist.de 85.13.141.74 IN 7107
NS onmylist.de ns5.kasserver.com IN 7200
NS onmylist.de ns6.kasserver.com IN 7200
MX onmylist.de w01ae1c0.kasserver.com IN 7200
TXT onmylist.de v=spf1 mx a ?all IN 7200

About Us

Contact Info

Follow Us

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