revision6 Webdesign
-
0Friendliness
-
0Performance
-
0Usability
-
0PWA
-
0Total
Mobile Friendliness 40/100
Configures the viewport
Content is sized correctly for the viewport
Size tap targets appropriately
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
URL |
---|
The tap target <div class="slider-mobile w-slider"></div> is close to 1 other tap targets final. |
The tap target <a href="/bc/misc" class="link-cat-blog">Misc</a> and 2 others are close to other tap targets. |
The tap target <a href="https://www.xi…nies/revision6" class="social-link-bl…w-inline-block"></a> and 3 others are close to other tap targets. |
... |
Uses legible font sizes
Color Contrast is satisfactory
Failing Elements
Impact | Snippet | Target | Failure Summary |
---|---|---|---|
serious | <a aria-label="learn more about cookies" role="button" tabindex="0" class="cc-link" href="https://www.revision6.de/datenschutz" rel="noopener noreferrer nofollow" target="_blank">Datenschutzerklärung lesen</a> | .cc-link | Fix any of the following: Element has insufficient color contrast of 3.17 (foreground color: #b12241, background color: #000000, font size: 12.0pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <div class="menu">Menü</div> | .menu | Fix any of the following: Element has insufficient color contrast of 2.05 (foreground color: #a9b0b8, background color: #f5f8fc, font size: 9.0pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <h2>Webdesign München</h2> | .no-lower-margin > .cont > h2 | Fix any of the following: Element has insufficient color contrast of 4.29 (foreground color: #de2c51, background color: #f5f8fc, font size: 9.3pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <p class="p-dachzeile minuskel grau">bei ihrer neuen Webagentur</p> | .minuskel | Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #77828f, background color: #f5f8fc, font size: 9.3pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <h2>Unser Workflow</h2> | .link-block-sec.w-inline-block[href$="webdesign-workflow"] > h2 | Fix any of the following: Element has insufficient color contrast of 4.29 (foreground color: #de2c51, background color: #f5f8fc, font size: 9.3pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <p>Und dennoch bestehen fundamental unterschiedliche Auffassungen darüber, welche Informationen hierfür zugeschnitten sein sollten. Deshalb ist es so wichtig, in diesem grundlegenden Schritt nicht aufs Geratewohl zu arbeiten, sondern mit analytischen Ansätzen an die Sache heranzugehen. </p> | #konzept-gestaltung > .w-col-7.w-col.w-clearfix > .rich.w-richtext > p:nth-child(1) | Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #77828f, background color: #f5f8fc, font size: 11.1pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <p> | #konzept-gestaltung > .w-col-7.w-col.w-clearfix > .rich.w-richtext > p:nth-child(2) | Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #77828f, background color: #f5f8fc, font size: 11.1pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <p> | #technische-realisierung > .w-col-7.w-col.w-clearfix > .rich.w-richtext > p:nth-child(1) | Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #77828f, background color: #f5f8fc, font size: 11.1pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <p>Neben ökonomischer Effizienz achten wir bei der Programmierung Ihrer Internetseite insbesondere auf eine technisch einwandfreie Umsetzung, die <a href="https://www.revision6.de/t/cms">einfache Wartung</a> und optimale Indizierung durch Suchmaschinen sicherstellt.</p> | #technische-realisierung > .w-col-7.w-col.w-clearfix > .rich.w-richtext > p:nth-child(2) | Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #77828f, background color: #f5f8fc, font size: 11.1pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <p>Das ist nur dann der Fall, wenn die Kosten pro Conversion (Lead, Produkt-Kauf, Vertragsabschluss, etc) auf ein vernünftiges Verhältnis optimiert sind.</p> | #seo-conversion-optimierung > .w-col-7.w-col.w-clearfix > .rich.w-richtext > p:nth-child(1) | Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #77828f, background color: #f5f8fc, font size: 11.1pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <p>Um die Website also als erfolgreiches Tool effizient nutzbar zu machen ist zum einen qualitativ und quantitativ hochwertiger Traffic nötig, der zum anderen Conversions produziert.</p> | #seo-conversion-optimierung > .w-col-7.w-col.w-clearfix > .rich.w-richtext > p:nth-child(2) | Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #77828f, background color: #f5f8fc, font size: 11.1pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <p> | .rich.w-richtext > p:nth-child(3) | Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #77828f, background color: #f5f8fc, font size: 11.1pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <h2>Klienten</h2> | .link-block-sec.w-inline-block[href$="cases"] > h2 | Fix any of the following: Element has insufficient color contrast of 4.29 (foreground color: #de2c51, background color: #f5f8fc, font size: 9.3pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <h2>Blog</h2> | section:nth-child(12) > .cont > h2 | Fix any of the following: Element has insufficient color contrast of 4.29 (foreground color: #de2c51, background color: #f5f8fc, font size: 9.3pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <h4>Können Sie Phishing-Mails erkennen?</h4> | .blog.w-col-6.w-dyn-item:nth-child(1) > .link-block-blog.w-inline-block > h4 | Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #77828f, background color: #f5f8fc, font size: 16.7pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <p class="p-dachzeile grau date-blog">Jan 23, 2019</p> | .blog.w-col-6.w-dyn-item:nth-child(1) > .w-clearfix > .date-blog.p-dachzeile.grau | Fix any of the following: Element has insufficient color contrast of 2.05 (foreground color: #a9b0b8, background color: #f5f8fc, font size: 9.3pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <h4>Waldo finden – mit Google AI</h4> | .blog.w-col-6.w-dyn-item:nth-child(2) > .link-block-blog.w-inline-block > h4 | Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #77828f, background color: #f5f8fc, font size: 16.7pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <p class="p-dachzeile grau date-blog">Aug 8, 2018</p> | .blog.w-col-6.w-dyn-item:nth-child(2) > .w-clearfix > .date-blog.p-dachzeile.grau | Fix any of the following: Element has insufficient color contrast of 2.05 (foreground color: #a9b0b8, background color: #f5f8fc, font size: 9.3pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <h4>Unser CDN-Anbieter schützt sich mittels Lava-Lampen vor Hackern</h4> | .blog.w-col-6.w-dyn-item:nth-child(3) > .link-block-blog.w-inline-block > h4 | Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #77828f, background color: #f5f8fc, font size: 16.7pt, font weight: normal). Expected contrast ratio of 4.5:1 |
serious | <p class="p-dachzeile grau date-blog">Aug 7, 2018</p> | .blog.w-col-6.w-dyn-item:nth-child(3) > .w-clearfix > .date-blog.p-dachzeile.grau | Fix any of the following: Element has insufficient color contrast of 2.05 (foreground color: #a9b0b8, background color: #f5f8fc, font size: 9.3pt, font weight: normal). Expected contrast ratio of 4.5:1 |
... |
Performance 67/100
Speed Index
-
Speed Index6131.45target < 4500 ms
Perceptual Speed Index is a page load performance metric that shows you how quickly the contents of a page are visibly populated. The lower the score, the better. Source: Lighthouse - Learn more
Document complete
-
Time7.7seconds
-
Resources53requests
-
Bytes in999.8KB
These metrics are collected from the initial request until the browser considers the page loaded (JavaScript onLoad event). This usually happens after all of the image content has loaded but may not include content that is triggered by javascript execution.
Fully load
-
Time7.7seconds
-
Resources58requests
-
Bytes in1020.6KB
These metrics are collected from the initial request until 2 seconds of no network activity after Document Complete (JavaScript onLoad event). This will usually include any activity that is triggered by javascript after the main page loads.
Assets by Domain
Requests
- uploads-ssl.webflow.com
- tracking24.net
- fonts.gstatic.com
- www.google.com
- cdnjs.cloudflare.com
- in.hotjar.com
- www.google-analytics.com
- www.revision6.de
- www.gstatic.com
- static.hotjar.com
- vars.hotjar.com
- script.hotjar.com
- fonts.googleapis.com
- ajax.googleapis.com
- stats.g.doubleclick.net
- d1tdp7z6w94jbb.cloudfront.net
Bytes downloaded
- uploads-ssl.webflow.com
- www.gstatic.com
- script.hotjar.com
- fonts.gstatic.com
- d1tdp7z6w94jbb.cloudfront.net
- www.google-analytics.com
- cdnjs.cloudflare.com
- www.revision6.de
- ajax.googleapis.com
- tracking24.net
- static.hotjar.com
- vars.hotjar.com
- www.google.com
- fonts.googleapis.com
- stats.g.doubleclick.net
- in.hotjar.com
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
- other
Bytes downloaded
- html
- js
- css
- image
- font
- other
Speed
Load time7714 ms
Page load is fast enough on 3G
First byte3230 ms
First Contentful Paint3060.3645 ms
First meaningful paint3756.047 ms
Estimated Input Latency12 ms (target < 50 ms)
Uses persistent connections (keep alive)Score: 100%
First CPU Idle3756.05 ms
Time to Interactive3756.05 ms
Page weight
Uses compression (gzip, zopfli, deflate, brotli)Score: 94%
Uses a CDN for all static assetsScore: 96%
Leverage browser caching
Leverage browser caching for the following cacheable resources:
URL |
---|
https://tracking24.net/tracking.js (expiration not specified) |
https://static.hotjar.com/c/hotjar-969875.js?sv=6 (60 seconds) |
https://www.google.com/recaptcha/api.js (5 minutes) |
https://www.google-analytics.com/analytics.js (2 hours) |
... |
Minify CSS
Minify HTML
Minify JavaScript
Minify JavaScript for the following resources to reduce their size by 373B (15% reduction).
URL |
---|
Minifying https://tracking24.net/tracking.js could save 373B (15% reduction) after compression. |
... |
Avoids an excessive DOM size338 nodes
-
Total DOM Nodes338target < 1,500 nodes
-
DOM Depth10target < 32
-
Maximum Children30target < 60 nodes
Compressed Images
Uses Progressive JPEGsScore: 0 %
Properly Sized ImagesPotential savings of 225 KB
Offscreen images
First impression
Eliminates render-blocking JavaScript and CSS in above-the-fold content
Your page has 3 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
URL |
---|
https://ajax.googleapis.com/ajax/libs/webfont/1.4.7/webfont.js |
https://cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.1.0/cookieconsent.min.js |
https://tracking24.net/tracking.js |
https://uploads-ssl.webflow.com/5b59ce0602a907c774718348/css/r666.f448f44a0.css |
https://fonts.googleapis.com/css?family=Zilla+Slab:regular,italic |
https://cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.1.0/cookieconsent.min.css |
... |
Prioritizes visible content
Improves server response time
Avoids landing page redirects
Usability 56/100 Industry: Agency / Portfolio
Brand logo linked to homepage
No ending trailing paths
Active section is highlighted in navigation menus
Listing/overview pages with many items implements deferred loading techniques
Prevent layout shiftings when loading media. Set width and height attributes on both <img> and <video> tags
The case listing page is not the only way to browse through all the casesNot applicable
Carousels are generally avoided (but they are acceptable if they are well implemented)
Make it easy to contact you
The most appropriate keyboard for the input type is provided first
All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real time
PWA / Best Practices 82/100
Avoids Application Cache
Avoids WebSQL DB
Avoids requesting the geolocation permission on page load
robots.txt is valid
Avoids requesting the notification permission on page load
Avoids deprecated APIs
Allows to paste into password input fields
Registers a Service Worker
Responds with a 200 when offline
Uses HTTPS
Redirects HTTP traffic to HTTPS
Uses HTTP/2 for its own resources
Uses passive listeners to improve scrolling performance
Avoid using document.write()
Manifest's short_name won't be truncated when displayed on homescreen
Configured for a custom splash screen
User can be prompted to Install the Web App
This report was built manually by Awwwards experts taking care personally of every detail using several Google and 3rd-party audit tools and services for metrics, web performance optimization and best practices for mobile design and development.
Loading time vary depending on network, device, server, site design, and implementation.
These are the environments used to create this report:
Webpagetest | Test Location | Dulles VA USA |
Browser | MotoG4 Chrome | |
Connection | Mobile 3G (1.6 Mbps / 768 Kbps 300ms RTT) | |
Number of Runs | 1 | |
User Agent | Default | |
Lighthouse | User agent | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 |
Device Emulation | Emulated Nexus 5X | |
Network Throttling | 150ms TCP RTT, 1,638.4 Kbps throughput (Simulated) | |
CPU Throttling | 4x slowdown (Simulated) | |
PageSpeed Insights | Environment | Mobile |