Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

veka.com

VEKA | World leading PVC extrusion | VEKA Group

Page Load Speed

6.4 sec in total

First Response

432 ms

Resources Loaded

4.6 sec

Page Rendered

1.4 sec

About Website

Welcome to veka.com homepage info - get ready to check VEKA best content for Japan right away, or after learning these important things about veka.com

For more than 50 years we have been producing PVC products for window construction, architecture & industry | learn more

Visit veka.com

Key Findings

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

Performance Metrics

veka.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value2,630 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

veka.com

432 ms

veka.com

441 ms

1129 ms

webforms_full_min_js.js

513 ms

loader.js

35 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 20% of them (8 requests) were addressed to the original Veka.com, 73% (29 requests) were made to Vekaprod-media.e-spirit.cloud and 5% (2 requests) were made to App.usercentrics.eu. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Vekaprod-media.e-spirit.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (56%)

Content Size

2.3 MB

After Optimization

1.0 MB

In fact, the total size of Veka.com main page is 2.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. 30% of websites need less resources to load. HTML takes 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 1.3 MB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 140.7 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. 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 1.3 MB or 90% of the original size.

Image Optimization

-4%

Potential reduce by 25.9 kB

  • Original 635.1 kB
  • After minification 609.3 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. VEKA images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 106 B

  • Original 255.2 kB
  • After minification 255.2 kB
  • After compression 255.1 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.

Requests Breakdown

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

Requests Now

37

After Optimization

29

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VEKA. 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

veka.com accessibility score

93

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

Best Practices

veka.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

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

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Veka.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Veka.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 VEKA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: