Tools & Wizards About Us
veka.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

veka.com

VEKA | World leading PVC extrusion | VEKA Group

Page Load Speed

3.9 sec in total

First Response

357 ms

Resources Loaded

3.4 sec

Page Rendered

153 ms

veka.com screenshot

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 357 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

veka.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value23.2 s

0/100

10%

TBT (Total Blocking Time)

Value8,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

veka.com

357 ms

worldwide.html

386 ms

stylesheet_389baa5807.css

101 ms

default.css

203 ms

jquery.lightbox-0.5.css

193 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 503.2 kB (24%)

Content Size

2.1 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Veka.com main page is 2.1 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. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 41.3 kB

  • Original 51.9 kB
  • After minification 48.9 kB
  • After compression 10.6 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 41.3 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 101.8 kB

  • Original 1.6 MB
  • After minification 1.5 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. VEKA images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 285.2 kB

  • Original 379.2 kB
  • After minification 301.7 kB
  • After compression 94.0 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 285.2 kB or 75% of the original size.

CSS Optimization

-87%

Potential reduce by 74.9 kB

  • Original 86.5 kB
  • After minification 55.0 kB
  • After compression 11.6 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. Veka.com needs all CSS files to be minified and compressed as it can save up to 74.9 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (31%)

Requests Now

68

After Optimization

47

  • Images
  • JavaScript
  • CSS

The browser has sent 68 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 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

veka.com

veka.com

357 ms

worldwide.html

worldwide.html

386 ms

stylesheet_389baa5807.css

stylesheet_389baa5807.css

101 ms

default.css

default.css

203 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

193 ms

dotcom.css

dotcom.css

194 ms

jquery-ui-1.8.14.custom.css

jquery-ui-1.8.14.custom.css

197 ms

default_font_size_m.css

default_font_size_m.css

942 ms

jquery-1.6.2.min.js

jquery-1.6.2.min.js

304 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

296 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

303 ms

jquery.areaoffset.js

jquery.areaoffset.js

302 ms

jquery-ui-1.8.14.custom.min.js

jquery-ui-1.8.14.custom.min.js

304 ms

jquery.cluetip.js

jquery.cluetip.js

392 ms

encoder.js

encoder.js

407 ms

dotcom.js

dotcom.js

406 ms

cufon-yui.js

cufon-yui.js

405 ms

Rotis.font.js

Rotis.font.js

403 ms

RotisExBd.font.js

RotisExBd.font.js

495 ms

default.js

default.js

510 ms

javascript_bd4d1f63e4.js

javascript_bd4d1f63e4.js

507 ms

jquery.validationEngine-de.js

jquery.validationEngine-de.js

499 ms

jquery.validationEngine.js

jquery.validationEngine.js

595 ms

form.js

form.js

590 ms

background_1920.jpg

background_1920.jpg

289 ms

veka_logo.png

veka_logo.png

105 ms

veka_claim_e.png

veka_claim_e.png

105 ms

1px.png

1px.png

103 ms

back.png

back.png

193 ms

world.png

world.png

573 ms

america_hover.png

america_hover.png

397 ms

asia_hover.png

asia_hover.png

398 ms

europe_hover.png

europe_hover.png

403 ms

00_america.png

00_america.png

493 ms

argentina.png

argentina.png

368 ms

brazil.png

brazil.png

467 ms

chile.png

chile.png

499 ms

usa.png

usa.png

500 ms

canada.png

canada.png

601 ms

00_asia.png

00_asia.png

853 ms

china.png

china.png

692 ms

india.png

india.png

603 ms

malaysia.png

malaysia.png

599 ms

singapore.png

singapore.png

665 ms

thailand.png

thailand.png

703 ms

00_europe.png

00_europe.png

906 ms

belgium.png

belgium.png

702 ms

bosniaandherzegovina.png

bosniaandherzegovina.png

760 ms

bulgaria.png

bulgaria.png

787 ms

croatia.png

croatia.png

804 ms

czechrepublic.png

czechrepublic.png

803 ms

france.png

france.png

854 ms

germany.png

germany.png

882 ms

greatbritain.png

greatbritain.png

900 ms

greece.png

greece.png

903 ms

italy.png

italy.png

957 ms

middleeast.png

middleeast.png

954 ms

netherlands.png

netherlands.png

979 ms

poland.png

poland.png

1000 ms

romania.png

romania.png

999 ms

russia.png

russia.png

912 ms

scandinavia.png

scandinavia.png

969 ms

serbia.png

serbia.png

971 ms

spain.png

spain.png

889 ms

switzerland.png

switzerland.png

840 ms

turkey.png

turkey.png

734 ms

ukraine.png

ukraine.png

718 ms

trennlinie_horizontal_dotted.png

trennlinie_horizontal_dotted.png

770 ms

tooltip_detail_arrow_left.png

tooltip_detail_arrow_left.png

769 ms

default_print.css

default_print.css

99 ms

Accessibility Review

veka.com accessibility score

98

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

button, link, and menuitem elements do not have accessible names.

Best Practices

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

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

    DE

  • 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 does not match the claimed German 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

veka.com

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