Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

kika.com

kika Onlineshop » Das Trendmöbelhaus für Österreich | kika

Page Load Speed

12 sec in total

First Response

327 ms

Resources Loaded

11.3 sec

Page Rendered

378 ms

About Website

Click here to check amazing Kika content for Poland. Otherwise, check out these important facts you probably never knew about kika.com

Günstige Möbel im kika Onlineshop kaufen: ✓ Boxspringbetten ✓ Ecksofas ✓ Esszimmerstühle ✓ Couchtische ✓ Küchenblöcke & mehr ➜ Jetzt entdecken

Visit kika.com

Key Findings

We analyzed Kika.com page load time and found that the first response time was 327 ms and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

kika.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value25.9 s

0/100

25%

SI (Speed Index)

Value17.2 s

0/100

10%

TBT (Total Blocking Time)

Value4,750 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.263

47/100

15%

TTI (Time to Interactive)

Value46.4 s

0/100

10%

Network Requests Diagram

kika.com

327 ms

www.kika.com

296 ms

101 ms

www.kika.at

263 ms

kika

552 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Kika.com, 71% (69 requests) were made to Kika.at and 5% (5 requests) were made to Media.kika.at. The less responsive or slowest element that took the longest time to load (5.6 sec) relates to the external source Data.de.coremetrics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (45%)

Content Size

3.2 MB

After Optimization

1.7 MB

In fact, the total size of Kika.com main page is 3.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. 60% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 271.9 kB

  • Original 304.0 kB
  • After minification 261.3 kB
  • After compression 32.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 42.7 kB, which is 14% 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 271.9 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 5.1 kB

  • Original 1.3 MB
  • After minification 1.3 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. Kika images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 884.3 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 354.8 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 884.3 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 286.3 kB

  • Original 339.6 kB
  • After minification 337.0 kB
  • After compression 53.3 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Kika.com needs all CSS files to be minified and compressed as it can save up to 286.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (62%)

Requests Now

87

After Optimization

33

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

Accessibility Review

kika.com accessibility score

81

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-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

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

Links do not have a discernible name

Best Practices

kika.com 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

kika.com SEO score

85

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

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kika.com 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 Kika.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Kika. 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: