Tools & Wizards About Us
weio.de screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

weio.de

Webdesign Landshut | Moderne Webseiten - MEDIAFOLIO.DE

Page Load Speed

3.9 sec in total

First Response

219 ms

Resources Loaded

2.9 sec

Page Rendered

869 ms

weio.de screenshot

About Website

Click here to check amazing Weio content. Otherwise, check out these important facts you probably never knew about weio.de

Webdesign Landshut - Wir entwickeln Ihre moderne Webseite, mit einem klaren Webdesign ohne störende Elemente.

Visit weio.de

Key Findings

We analyzed Weio.de page load time and found that the first response time was 219 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

weio.de performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

weio.de

219 ms

mediafolio.de

789 ms

frontend.min.css

219 ms

css

28 ms

astra-local-fonts.css

325 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Weio.de, 96% (65 requests) were made to Mediafolio.de and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (932 ms) relates to the external source Mediafolio.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.3 kB (19%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images

In fact, the total size of Weio.de main page is 1.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 268.4 kB

  • Original 313.6 kB
  • After minification 308.5 kB
  • After compression 45.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 268.4 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 1.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Weio images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 50 (77%)

Requests Now

65

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

weio.de

weio.de

219 ms

mediafolio.de

mediafolio.de

789 ms

frontend.min.css

frontend.min.css

219 ms

css

css

28 ms

astra-local-fonts.css

astra-local-fonts.css

325 ms

frontend.css

frontend.css

332 ms

cookieblocker.min.css

cookieblocker.min.css

326 ms

header-footer-elementor.css

header-footer-elementor.css

337 ms

elementor-icons.min.css

elementor-icons.min.css

339 ms

frontend.min.css

frontend.min.css

452 ms

swiper.min.css

swiper.min.css

443 ms

post-1215.css

post-1215.css

442 ms

frontend.min.css

frontend.min.css

671 ms

uael-frontend.min.css

uael-frontend.min.css

684 ms

wpforms-base.min.css

wpforms-base.min.css

466 ms

all.min.css

all.min.css

557 ms

v4-shims.min.css

v4-shims.min.css

554 ms

post-7.css

post-7.css

568 ms

general.min.css

general.min.css

582 ms

eael-1019.css

eael-1019.css

667 ms

post-1019.css

post-1019.css

668 ms

astra-addon-66890aea558175-81330286.css

astra-addon-66890aea558175-81330286.css

704 ms

fontawesome.min.css

fontawesome.min.css

705 ms

regular.min.css

regular.min.css

776 ms

solid.min.css

solid.min.css

776 ms

jquery.min.js

jquery.min.js

787 ms

jquery-migrate.min.js

jquery-migrate.min.js

796 ms

v4-shims.min.js

v4-shims.min.js

800 ms

js

js

73 ms

frontend.min.js

frontend.min.js

842 ms

frontend.min.js

frontend.min.js

842 ms

general.min.js

general.min.js

841 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

844 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

844 ms

wp-polyfill.min.js

wp-polyfill.min.js

908 ms

dom-ready.min.js

dom-ready.min.js

909 ms

main.js

main.js

925 ms

astra-addon-66890aea55c846-84605232.js

astra-addon-66890aea55c846-84605232.js

932 ms

complianz.min.js

complianz.min.js

823 ms

frontend.js

frontend.js

728 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

794 ms

webpack.runtime.min.js

webpack.runtime.min.js

787 ms

frontend-modules.min.js

frontend-modules.min.js

806 ms

hooks.min.js

hooks.min.js

809 ms

i18n.min.js

i18n.min.js

715 ms

frontend.min.js

frontend.min.js

725 ms

waypoints.min.js

waypoints.min.js

773 ms

core.min.js

core.min.js

766 ms

frontend.min.js

frontend.min.js

703 ms

elements-handlers.min.js

elements-handlers.min.js

705 ms

underscore.min.js

underscore.min.js

703 ms

wp-util.min.js

wp-util.min.js

701 ms

frontend.min.js

frontend.min.js

684 ms

lazyload.min.js

lazyload.min.js

677 ms

cropped-mediafolio_Logo-300x45.png

cropped-mediafolio_Logo-300x45.png

537 ms

astra.woff

astra.woff

442 ms

happy_working_webdesign-768x768.jpg

happy_working_webdesign-768x768.jpg

217 ms

luca-bravo-ujhkqutt3f0-unsplash-768x512.jpeg

luca-bravo-ujhkqutt3f0-unsplash-768x512.jpeg

218 ms

FOTOFOLIO-DE-768x516.png

FOTOFOLIO-DE-768x516.png

456 ms

FOTOFOLIO-DE-SHOP-768x502.png

FOTOFOLIO-DE-SHOP-768x502.png

236 ms

mentaldriveacademy-de-768x468.png

mentaldriveacademy-de-768x468.png

448 ms

printfolio-de-screenshot-referenz-webdesign-weio-de-768x500.png

printfolio-de-screenshot-referenz-webdesign-weio-de-768x500.png

236 ms

emotionsraum-de-768x479.png

emotionsraum-de-768x479.png

433 ms

ajeti-de-768x447.png

ajeti-de-768x447.png

434 ms

Referenzprojekt_Webdesign_02-768x483.jpg

Referenzprojekt_Webdesign_02-768x483.jpg

353 ms

Referenzprojekt_Webdesign_01-768x467.jpg

Referenzprojekt_Webdesign_01-768x467.jpg

353 ms

posterfolio_Bild_mit_Logo-scaled-1-1024x768.jpg

posterfolio_Bild_mit_Logo-scaled-1-1024x768.jpg

577 ms

amy-leigh-barnard-jgutwvt0qkk-unsplash-768x512.jpeg

amy-leigh-barnard-jgutwvt0qkk-unsplash-768x512.jpeg

580 ms

Accessibility Review

weio.de accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

weio.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

weio.de SEO score

100

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weio.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Weio.de main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

weio.de

Open Graph data is detected on the main page of Weio. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: