Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

vea.re

Home | Lukas Oppermann — Lead UI/UX Design & Creative Technologist

Page Load Speed

123 ms in total

First Response

12 ms

Resources Loaded

27 ms

Page Rendered

84 ms

vea.re screenshot

About Website

Visit vea.re now to see the best up-to-date Vea content and also check out these interesting facts you probably never knew about vea.re

Lukas Oppermann is a design lead and creative director from berlin, germany. He loves creating experiences with a focus on usability.

Visit vea.re

Key Findings

We analyzed Vea.re page load time and found that the first response time was 12 ms and then it took 111 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

vea.re performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value8,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.961

2/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

vea.re

12 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Vea.re and no external sources were called. The less responsive or slowest element that took the longest time to load (12 ms) belongs to the original domain Vea.re.

Page Optimization Overview & Recommendations

Page size can be reduced by 20 B (15%)

Content Size

134 B

After Optimization

114 B

In fact, the total size of Vea.re main page is 134 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 134 B which makes up the majority of the site volume.

HTML Optimization

-15%

Potential reduce by 20 B

  • Original 134 B
  • After minification 134 B
  • After compression 114 B

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 20 B or 15% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

vea.re accessibility score

97

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

vea.re 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

SEO Factors

vea.re 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

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vea.re can be misinterpreted by Google and other search engines. Our service has detected that English 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 Vea.re main page’s claimed encoding is . 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 Vea. 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: