Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 0

    Best Practices

  • 62

    SEO

    Google-friendlier than
    22% of websites

heo.com

heo.com: Großhandel für Figuren, Spielwaren, Merchandising-Artikeln, Modellen, Textilien, Statuen, Spielen, Nachbildungen, Repliken & mehr

Page Load Speed

149.8 sec in total

First Response

820 ms

Resources Loaded

73.6 sec

Page Rendered

75.4 sec

heo.com screenshot

About Website

Visit heo.com now to see the best up-to-date Heo content for Austria and also check out these interesting facts you probably never knew about heo.com

Entdecken, shoppen und einkaufen bei heo.com: Günstige Preise für Figuren, Spielwaren, Merchandising-Artikeln, Modellen, Textilien, Statuen, Spielen, Nachbildungen, Repliken & mehr

Visit heo.com

Key Findings

We analyzed Heo.com page load time and found that the first response time was 820 ms and then it took 149 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 10 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

heo.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value27.1 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value2,960 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value24.9 s

0/100

10%

Network Requests Diagram

heo.com

820 ms

www.heo.com

1273 ms

en

276 ms

critical.css

154 ms

loadCSS.min.js

430 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 59% of them (36 requests) were addressed to the original Heo.com, 30% (18 requests) were made to Heomedia.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (59.7 sec) relates to the external source S.ytimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.4 MB (65%)

Content Size

5.3 MB

After Optimization

1.8 MB

In fact, the total size of Heo.com main page is 5.3 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. 70% of websites need less resources to load. Javascripts take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 470.0 kB

  • Original 500.1 kB
  • After minification 389.0 kB
  • After compression 30.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. This page needs HTML code to be minified as it can gain 111.1 kB, which is 22% 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 470.0 kB or 94% of the original size.

Image Optimization

-0%

Potential reduce by 1.4 kB

  • Original 933.4 kB
  • After minification 932.0 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. Heo images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 3.0 MB

  • Original 3.9 MB
  • After minification 3.8 MB
  • After compression 883.2 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 3.0 MB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (42%)

Requests Now

48

After Optimization

28

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

Accessibility Review

heo.com accessibility score

57

Accessibility Issues

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-*] attributes do not match their roles

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

SEO Factors

heo.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heo.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Heo.com 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 description is not detected on the main page of Heo. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: