Your Website Score is

Similar Ranking

52
VERSICHERUNG, VORSORGE UND VERMÖGENSAUFBAU | ALLIANZ
allianz.de
51
BUFFED - DAS PORTAL FÜR ONLINE-SPIELE, FILME, SERIEN & NERD-KRAMS
buffed.de
51
HOME | HEYHOBBY.NET
heyhobby.de
51
RENT PREMIUM FURNITURE & HOME APPLIANCES ONLINE - CITYFURNISH
cityfurnish.com
51
KINO OHNE TALENT - HOME
kot.de

Latest Sites

3
HUNDESCHULE SPÜRSINN
laufmithund.de
14
MAINTENANCE PAGE - MY BLOG
gesunds.de
23
GUSTAV SCHMIDT » IHR EXPERTE FÜR INDUSTRIE, WERKSTATT & CO.
gustav-schmidt.de
19
STARTSEITE
optiflex.de
36
SCHLÄUCHE, ARMATUREN, HYDRAULIK ... UND VIELES MEHR ...- SCHMITZ SIEGEN
schmitzsiegen.de
11
THE PAGE IS TEMPORARILY UNAVAILABLE
pro-media.org

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

52 allianz.de Last Updated: 3 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 65%
Best Practices Desktop Score 81%
SEO Desktop Score 83%
PWA Desktop Score 29%
Performance Mobile Score 17%
Best Practices Mobile Score 81%
SEO Mobile Score 86%
PWA Mobile Score 38%
Page Authority Authority 54%
Domain Authority Domain Authority 66%
Moz Rank 5.4/10
Bounce Rate Rate 0%
Title Tag 52 Characters
VERSICHERUNG, VORSORGE UND VERMÖGENSAUFBAU | ALLIANZ
Meta Description 144 Characters
Vertrauen Sie für Ihre Versicherungen auf mehr als 125 Jahre Qualität und Finanzstärke. Schließen Sie jetzt Ihre Allianz Versicherung online ab!
Effective URL 26 Characters
https://www.allianz.de:443
Excerpt Page content
Versicherung, Vorsorge und Vermögensaufbau | Allianz ...
Keywords Cloud Density
chat41 live41 starten40 überblick31 allianz28 meine27 kostenlos21 berechnen19 melden18 hotline18
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
chat 41
live 41
starten 40
überblick 31
allianz 28
meine 27
kostenlos 21
berechnen 19
melden 18
hotline 18
Google Preview Your look like this in google search result
VERSICHERUNG, VORSORGE UND VERMÖGENSAUFBAU | ALLIANZ
https://www.allianz.de:443
Vertrauen Sie für Ihre Versicherungen auf mehr als 125 Jahre Qualität und Finanzstärke. Schließen Sie jetzt Ihre Allianz Versicherung online ab!
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~675.91 KB
Code Size: ~588.4 KB
Text Size: ~87.51 KB Ratio: 12.95%

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
Largest Contentful Paint element 1,190 ms
This is the largest contentful element painted within the viewport
Largest Contentful Paint 1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Total Blocking Time 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 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)
Max Potential First Input Delay 270 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid large layout shifts 1 element 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)
Defer offscreen images Potential savings of 83 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Time to Interactive 3.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Minimize main-thread work 2.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 220 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 152 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
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
Initial server response time was short Root document took 10 ms
Keep the server response time for the main document short because all other requests depend on it
Properly size images Potential savings of 294 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid enormous network payloads Total size was 2,732 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 40 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
Network Round Trip Times 20 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 images in next-gen formats Potential savings of 220 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid chaining critical requests 36 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 deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Avoid an excessive DOM size 3,193 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 static assets with an efficient cache policy 24 resources found
A long cache lifetime can speed up repeat visits to your page
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Reduce unused JavaScript Potential savings of 385 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Speed Index 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 330 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minify JavaScript Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Reduce JavaScript execution time 1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Mobile

Mobile Screenshot
Reduce unused JavaScript Potential savings of 384 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Network Round Trip Times 90 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
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
Initial server response time was short Root document took 10 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid large layout shifts 3 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 enormous network payloads Total size was 2,556 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Avoid large layout shifts 6 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)
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 15.8 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 25 resources found
A long cache lifetime can speed up repeat visits to your page
Cumulative Layout Shift 0.478
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce unused CSS Potential savings of 152 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Minimize main-thread work 10.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid serving legacy JavaScript to modern browsers Potential savings of 40 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
Speed Index 9.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce JavaScript execution time 6.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 290 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
First Meaningful Paint 3.2 s
First Meaningful Paint measures when the primary content of a page is visible
Properly size images Potential savings of 206 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 5.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Minify JavaScript Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Total Blocking Time 3,780 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Max Potential First Input Delay 970 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
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
Defer offscreen images Potential savings of 83 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
First Contentful Paint 3.1 s
First Contentful Paint marks the time at which the first text or image is painted
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 an excessive DOM size 3,193 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 4,960 ms
This is the largest contentful element painted within the viewport
Eliminate render-blocking resources Potential savings of 1,750 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 36 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 deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser

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.
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/2 200 
content-type: text/html; charset=UTF-8
date: Tue, 23 Apr 2024 19:10:05 GMT
server: Apache
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: frame-ancestors 'self' azd.marketing.adobe.com
etag: "c8150498ba0126fcbd82645db0d8aefa-gzip"
accept-ranges: bytes
content-encoding: gzip
expires: Tue, 23 Apr 2024 19:10:10 GMT
cache-control: max-age=5
vary: Host,Accept-Encoding
x-cache: Hit from cloudfront
via: 1.1 444c86780ce99d2fc729208a25cb6aa2.cloudfront.net (CloudFront)
x-amz-cf-pop: WAW51-P2
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: bNetec3O89t_fGN_2Q9JpnJiZYKgE3QVFDd3cfxco5ZF6GVLINKVKw==
age: 4056
DNS Records DNS Resource Records associated with a hostname
View DNS Records