Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

gea.at

Schuhe, Taschen und Möbel, Made im Waldviertel • GEA Waldviertler

Page Load Speed

3.3 sec in total

First Response

398 ms

Resources Loaded

2.4 sec

Page Rendered

453 ms

gea.at screenshot

About Website

Welcome to gea.at homepage info - get ready to check GEA best content right away, or after learning these important things about gea.at

Schuhe, Taschen, Naturmöbel und Matratzen. Erhältlich in mehr als 50 Läden in AT, DE und der Schweiz, sowie in unserem Online-Shop.

Visit gea.at

Key Findings

We analyzed Gea.at page load time and found that the first response time was 398 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

gea.at performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value3.3 s

94/100

10%

Network Requests Diagram

gea.at

398 ms

gea-waldviertler.at

644 ms

gea-bundle.css

340 ms

jquery.min.js

530 ms

bootstrap.bundle.min.js

556 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Gea.at, 97% (33 requests) were made to Gea-waldviertler.at. The less responsive or slowest element that took the longest time to load (850 ms) relates to the external source Gea-waldviertler.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (98%)

Content Size

1.2 MB

After Optimization

23.3 kB

In fact, the total size of Gea.at main page is 1.2 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. 25% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 51.1 kB

  • Original 58.6 kB
  • After minification 44.0 kB
  • After compression 7.5 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. This page needs HTML code to be minified as it can gain 14.5 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 51.1 kB or 87% of the original size.

Image Optimization

-99%

Potential reduce by 1.1 MB

  • Original 1.1 MB
  • After minification 15.8 kB

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. Obviously, GEA needs image optimization as it can save up to 1.1 MB or 99% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 8 (25%)

Requests Now

32

After Optimization

24

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

Accessibility Review

gea.at accessibility score

76

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

gea.at best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

gea.at SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Gea.at 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 Gea.at 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

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