Your Website Score is
SEO Rank : 14 Website URL: geniusworld.de Last Updated: 1 month
Success
39% of passed verification steps
Warning
15% of total warning
Errors
46% of total errors, require fast action
Share
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
Mobile
Moz Authority Rank
Page Authority
Authority 20%
Domain Authority
Domain Authority 3%
Moz Rank
2.0/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
56 Characters
GEWINNSPIELFORUM - TÄGLICH NEUE UND SERIÖSE GEWINNSPIELE
Meta Description
0 Characters
NO DATA
Effective URL
22 Characters
https://geniusworld.de
Excerpt
Page content
Gewinnspielforum - Täglich neue und seriöse Gewinnspiele
...
Google Preview
Your look like this in google search result
GEWINNSPIELFORUM - TÄGLICH NEUE UND SERIÖSE GEWINNSPIELE
https://geniusworld.de
Gewinnspielforum - Täglich neue und seriöse Gewinnspiele
...
Robots.txt
File No Found
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~70.21 KB
Code Size: ~52.37 KB
Text Size: ~17.84 KB Ratio: 25.40%
Social Data
Desktop
Initial server response time was short
Root document took 140 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid chaining critical requests
15 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
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
First CPU Idle
1.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Avoids enormous network payloads
Total size was 315 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index
0.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve static assets with an efficient cache policy
12 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted
JavaScript execution time
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
Potential savings of 790 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
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
Enable text compression
Potential savings of 81 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Remove unused CSS
Potential savings of 18 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Minify JavaScript
Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Keep request counts low and transfer sizes small
22 requests • 315 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint
1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities
5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Time to Interactive
1.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Meaningful Paint
1.0 s
First Meaningful Paint measures when the primary content of a page is visible
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.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Estimated Input Latency
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Avoids an excessive DOM size
793 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)
Remove unused JavaScript
Potential savings of 53 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minimizes main-thread work
0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Mobile
Minify JavaScript
Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Initial server response time was short
Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources
Potential savings of 2,480 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Meaningful Paint
3.9 s
First Meaningful Paint measures when the primary content of a page is visible
Total Blocking Time
40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
JavaScript execution time
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks
2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Estimated Input Latency
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
First CPU Idle
3.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
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 chaining critical requests
15 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
Document uses legible font sizes
97.5% 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
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
Time to Interactive
4.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve static assets with an efficient cache policy
12 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay
140 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Largest Contentful Paint
3.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Keep request counts low and transfer sizes small
22 requests • 314 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Remove unused CSS
Potential savings of 19 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Avoids an excessive DOM size
793 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)
Avoids enormous network payloads
Total size was 314 KiB
Large network payloads cost users real money and are highly correlated with long load times
Includes front-end JavaScript libraries with known security vulnerabilities
5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First Contentful Paint
3.2 s
First Contentful Paint marks the time at which the first text or image is painted
Remove unused JavaScript
Potential savings of 53 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minimize third-party usage
Third-party code blocked the main thread for 20 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
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
First Contentful Paint (3G)
6615 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Tap targets are not sized appropriately
71% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Enable text compression
Potential savings of 81 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Speed Index
3.2 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Warning! Your site not 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
Warning! You have broken links
View links
Alexa Rank
0
Local Rank: / Users: / PageViews:
Global Rank
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| geniusworld.co | Already Registered |
| geniusworld.us | Already Registered |
| geniusworld.com | Already Registered |
| geniusworld.org | Already Registered |
| geniusworld.net | Already Registered |
| gniusworld.de | Already Registered |
| teniusworld.de | Already Registered |
| beniusworld.de | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Tue, 19 Jan 2021 08:15:57 GMT
server: Apache
cache-control: no-cache, private
content-encoding: gzip
set-cookie: mybb[lastvisit]=1611044157; expires=Wed, 19-Jan-2022 08:15:57 GMT; path=/; domain=.geniusworld.de
set-cookie: mybb[lastactive]=1611044157; expires=Wed, 19-Jan-2022 08:15:57 GMT; path=/; domain=.geniusworld.de
set-cookie: sid=2d127bcda443c776427bfce40a84c8c6; path=/; domain=.geniusworld.de; HttpOnly
content-type: text/html; charset=UTF-8
Click to Add/Show Comments