6.4 sec in total
432 ms
4.6 sec
1.4 sec
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.comWe 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.
veka.com performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value6.4 s
9/100
25%
Value13.2 s
2/100
10%
Value2,630 ms
4/100
30%
Value0
100/100
15%
Value16.1 s
6/100
10%
432 ms
441 ms
1129 ms
513 ms
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 size can be reduced by 1.3 MB (56%)
2.3 MB
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.
Potential reduce by 1.3 MB
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.
Potential reduce by 25.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. VEKA images are well optimized though.
Potential reduce by 106 B
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.
Number of requests can be reduced by 8 (22%)
37
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.
veka.com
432 ms
veka.com
441 ms
1129 ms
webforms_full_min_js.js
513 ms
loader.js
35 ms
gtm.js
102 ms
logo_veka-aktiengesellschaft.svg
432 ms
veka-welcome-center_innenhof_res_1_1_w400.jpg
569 ms
ref-gealan-villa-novigrad-kroatien-aussen-s9000_res_3_2_w390.jpg
529 ms
veka-png-logo_res_logo_h100.png
434 ms
gealan_logo_rgb_res_logo_h100.png
432 ms
bagger-altfenster_res_3_2_w390.jpg
907 ms
logo-veka-recycling_res_logo_h100.png
526 ms
ref-wohnmobil-vekaplan-s-inside_res_3_2_w390.jpg
909 ms
vekaplan_blue_res_logo_h100.png
835 ms
ref-vekadeck-khaki-girl_res_3_2_w390.jpg
1020 ms
vekaolp_logo_h100_res_logo_h100.png
917 ms
hotel_lighthouse-buesum-de-spectral-anthrazit-ultramatt-1_res_3_2_w390.jpg
1062 ms
spectral_black_res_logo_h100.png
1234 ms
logo_gealan-acrylcolor_small_res_logo_h100.png
1317 ms
windo-planning-pc_res_3_2_w390.jpg
1120 ms
dbs_orig_grey_res_logo_h100.png
1312 ms
texino-smart-home-familie_res_3_2_w390.jpg
1528 ms
logo_texino_rgb_graugruen_claim_res_logo_h100.png
1477 ms
icon-euro-sign-grey_res_logo_h100.png
1530 ms
icon-employees-grey-2_res_logo_h100.png
1632 ms
icon-window-grey_res_logo_h100.png
1429 ms
icon-location-pin-grey_res_logo_h100.png
1717 ms
icon-factory-grey_res_logo_h100.png
1835 ms
icon-recycle-grey_res_logo_h100.png
1868 ms
recyclinganlage_res_3_2_w690.jpg
1905 ms
sendenhorst_wiese_silos_res_4_3_w540.jpg
1632 ms
fensterbau_banner_res_4_3_w540.jpg
2017 ms
gealan_top-100_res_4_3_w540.jpg
2135 ms
bundle.js
9 ms
2fab0fa.js
1249 ms
1d6efe2.js
1066 ms
a9864df.js
1010 ms
0cad5c1.js
1412 ms
0c958c1.js
939 ms
veka.com accessibility score
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
Buttons do not have an accessible name
veka.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
veka.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
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.
veka.com
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: