Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

laviva.com

Territory | Home

Page Load Speed

3.2 sec in total

First Response

239 ms

Resources Loaded

1.7 sec

Page Rendered

1.2 sec

About Website

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

Territory ist die Agentur für Markeninhalte. Wir bieten Content, Influencer, Social-Media-Marketing, Mediaplanung sowie das Betreiben von eigenen Plattform Lösungen - alles aus einer Hand.

Visit laviva.com

Key Findings

We analyzed Laviva.com page load time and found that the first response time was 239 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

laviva.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

laviva.com

239 ms

de

113 ms

styles.css

96 ms

swiper-element-bundle.min.js

287 ms

gtm.js

63 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Laviva.com, 77% (17 requests) were made to Territory.de and 9% (2 requests) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (734 ms) relates to the external source Territory.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 48.9 kB (42%)

Content Size

117.3 kB

After Optimization

68.4 kB

In fact, the total size of Laviva.com main page is 117.3 kB. 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. HTML takes 60.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 48.6 kB

  • Original 60.5 kB
  • After minification 53.5 kB
  • After compression 11.9 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 7.0 kB, which is 12% 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 48.6 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 333 B

  • Original 3.2 kB
  • After minification 2.9 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. Laviva images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 12 B

  • Original 47.4 kB
  • After minification 47.4 kB
  • After compression 47.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 6.2 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.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Laviva. According to our analytics all requests are already optimized.

Accessibility Review

laviva.com accessibility score

96

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.

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

laviva.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

laviva.com 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 Laviva.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 Laviva.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 data is detected on the main page of Laviva. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: