2.8 sec in total
197 ms
2.6 sec
60 ms
Click here to check amazing 2A content. Otherwise, check out these important facts you probably never knew about 2a.be
2A architecten is een multidisciplinair architectenbureau met aandacht voor architectuur, budget, technieken en milieu.
Visit 2a.beWe analyzed 2a.be page load time and found that the first response time was 197 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
2a.be performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value6.3 s
10/100
25%
Value3.9 s
82/100
10%
Value210 ms
88/100
30%
Value0.028
100/100
15%
Value9.1 s
33/100
10%
197 ms
36 ms
35 ms
1034 ms
67 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 2a.be, 38% (20 requests) were made to Static.parastorage.com and 31% (16 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Polyfill-fastly.io.
Page size can be reduced by 359.6 kB (49%)
733.8 kB
374.2 kB
In fact, the total size of 2a.be main page is 733.8 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. 40% of websites need less resources to load. HTML takes 449.5 kB which makes up the majority of the site volume.
Potential reduce by 356.0 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 356.0 kB or 79% of the original size.
Potential reduce by 0 B
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. 2A images are well optimized though.
Potential reduce by 3.6 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.
Number of requests can be reduced by 11 (34%)
32
21
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2A. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
www.2a.be
197 ms
minified.js
36 ms
focus-within-polyfill.js
35 ms
polyfill.min.js
1034 ms
thunderbolt-commons.90d0afc1.bundle.min.js
67 ms
main.456d8521.bundle.min.js
67 ms
main.renderer.1d21f023.bundle.min.js
67 ms
lodash.min.js
72 ms
react.production.min.js
71 ms
react-dom.production.min.js
72 ms
siteTags.bundle.min.js
70 ms
wix-perf-measure.umd.min.js
70 ms
0284c9_bdd004ab4fb44c0c881db87f9b1cc05f~mv2.jpg
391 ms
0284c9_30a64a1ceefe4808af07ffeb1a721b77~mv2_d_5184_3456_s_4_2.jpg
400 ms
0284c9_00f8b38f5746484ab308b737cbf2e5ba~mv2_d_2448_3264_s_4_2.jpg
452 ms
0284c9_13a0e3ac6fe04f9e9bcf4398e87fc3e1~mv2_d_5184_3456_s_4_2.jpg
504 ms
0284c9_26a235f994714afaa19434c53844a58f~mv2_d_2448_2448_s_4_2.jpg
343 ms
0284c9_ce11cdb12b6149d29780f632d26f9917~mv2_d_5184_3456_s_4_2.jpg
453 ms
0284c9_72b6789388484433b0093d443444bf76~mv2_d_5184_3456_s_4_2.jpg
672 ms
0284c9_491c6014429149c19b3800c2b7d1d0fd~mv2_d_4925_3283_s_4_2.jpg
640 ms
0284c9_a3ab0eba021b4ab3be64ae8a50641668~mv2_d_5184_3456_s_4_2.jpg
710 ms
0284c9_95693e1cd0f341f0a551029973d7c76f~mv2_d_5122_3415_s_4_2.jpg
738 ms
0284c9_1e95fa2ff2494eae9027c7fb842398d1~mv2_d_5184_3456_s_4_2.jpg
738 ms
0284c9_6c80ed444a574aceb89c9c85ffb73b3a~mv2_d_4640_3480_s_4_2.jpg
754 ms
Wim%20Wijckmans-1.jpg
905 ms
0284c9_8e3a5b6d187e4b99b061184563a6a70e~mv2_d_5184_3456_s_4_2.jpg
914 ms
0284c9_51d4295f408f4a1f8dcc7802f1b33511~mv2_d_5184_3456_s_4_2.jpg
975 ms
0284c9_b448b8c7b84641f4a353f21c03fb2946~mv2_d_3716_2508_s_4_2.jpg
934 ms
bundle.min.js
129 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
14 ms
6849614c-986c-45b1-a1a7-39c891759bb9.woff
13 ms
80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff
12 ms
61bd362e-7162-46bd-b67e-28f366c4afbe.woff
12 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
13 ms
b56b944e-bbe0-4450-a241-de2125d3e682.woff
22 ms
6f8d1983-4d34-4fa4-9110-988f6c495757.woff
46 ms
117 ms
110 ms
112 ms
110 ms
106 ms
107 ms
145 ms
141 ms
139 ms
139 ms
137 ms
132 ms
deprecation-en.v5.html
6 ms
bolt-performance
29 ms
deprecation-style.v5.css
10 ms
right-arrow.svg
9 ms
2a.be accessibility score
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
[aria-*] attributes do not match their roles
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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
2a.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
2a.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2a.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that 2a.be 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.
2a.be
Open Graph data is detected on the main page of 2A. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: