4.6 sec in total
1 sec
3.2 sec
443 ms
Welcome to aebr.eu homepage info - get ready to check AEBR best content right away, or after learning these important things about aebr.eu
The latest news from the Association of European Border Regions (AEBR). Inform yourself about our services, initiatives, task forces and events. Read more!
Visit aebr.euWe analyzed Aebr.eu page load time and found that the first response time was 1 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
aebr.eu performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.3 s
22/100
25%
Value6.2 s
44/100
10%
Value170 ms
93/100
30%
Value0
100/100
15%
Value5.2 s
74/100
10%
1019 ms
97 ms
46 ms
191 ms
256 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 58% of them (29 requests) were addressed to the original Aebr.eu, 24% (12 requests) were made to C0.wp.com and 4% (2 requests) were made to I1.wp.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Aebr.eu.
Page size can be reduced by 117.8 kB (12%)
995.6 kB
877.9 kB
In fact, the total size of Aebr.eu main page is 995.6 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. 50% of websites need less resources to load. Images take 686.3 kB which makes up the majority of the site volume.
Potential reduce by 37.3 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. This page needs HTML code to be minified as it can gain 6.3 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 37.3 kB or 81% of the original size.
Potential reduce by 70.4 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. AEBR images are well optimized though.
Potential reduce by 7.4 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.
Potential reduce by 2.7 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. Aebr.eu has all CSS files already compressed.
Number of requests can be reduced by 33 (77%)
43
10
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AEBR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.aebr.eu
1019 ms
wp-emoji-release.min.js
97 ms
style.min.css
46 ms
styles.css
191 ms
wpcf7-redirect-frontend.min.css
256 ms
frontend.css
254 ms
bootstrap.min.css
350 ms
style.css
273 ms
unsemantic-grid-responsive-tablet.css
287 ms
jetpack.css
49 ms
jquery.min.js
53 ms
jquery-migrate.min.js
48 ms
bootstrap.min.js
288 ms
scripts.js
337 ms
photon.min.js
47 ms
wp-polyfill.min.js
50 ms
hooks.min.js
50 ms
i18n.min.js
52 ms
lodash.min.js
53 ms
url.min.js
51 ms
api-fetch.min.js
52 ms
index.js
335 ms
wpcf7-redirect-frontend-script.js
360 ms
intersectionobserver-polyfill.min.js
378 ms
lazy-images.min.js
379 ms
wp-embed.min.js
51 ms
e-202437.js
50 ms
css2
32 ms
all.min.css
237 ms
reset.css
149 ms
AEBRmap2011finalversion.jpg
279 ms
interreg.jpg
629 ms
AEBR-logo-e1591121740609.jpg
599 ms
interventures.jpg
261 ms
bsolutions.jpg
269 ms
LOGO-AEBR.svg
317 ms
en-flag.svg
315 ms
map-10.png
735 ms
wp-polyfill-fetch.min.js
96 ms
wp-polyfill-dom-rect.min.js
105 ms
wp-polyfill-url.min.js
103 ms
wp-polyfill-formdata.min.js
141 ms
wp-polyfill-element-closest.min.js
161 ms
wp-polyfill-object-fit.min.js
180 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk37cxsBw.ttf
39 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk3CstsBw.ttf
52 ms
fa-solid-900.woff
463 ms
fa-regular-400.woff
575 ms
fa-light-300.woff
570 ms
fa-brands-400.woff
443 ms
aebr.eu accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
aebr.eu 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
aebr.eu 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
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aebr.eu 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 Aebr.eu 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.
aebr.eu
Open Graph data is detected on the main page of AEBR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: