10.1 sec in total
441 ms
8.9 sec
742 ms
Click here to check amazing Living In content. Otherwise, check out these important facts you probably never knew about living-in.eu
In times when cities and communities are looking to digital solutions to tackle a growing range of interconnected challenges, we must boost these efforts through a ‘European Way’ where digital solutio...
Visit living-in.euWe analyzed Living-in.eu page load time and found that the first response time was 441 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
living-in.eu performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value9.4 s
0/100
25%
Value17.6 s
0/100
10%
Value2,650 ms
4/100
30%
Value0.043
99/100
15%
Value11.5 s
18/100
10%
441 ms
5012 ms
125 ms
107 ms
407 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 62% of them (48 requests) were addressed to the original Living-in.eu, 15% (12 requests) were made to Player.vimeo.com and 10% (8 requests) were made to I.vimeocdn.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Living-in.eu.
Page size can be reduced by 193.2 kB (8%)
2.3 MB
2.1 MB
In fact, the total size of Living-in.eu 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 59.2 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 59.2 kB or 82% of the original size.
Potential reduce by 103.7 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. Living In images are well optimized though.
Potential reduce by 30.2 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 30.2 kB or 59% of the original size.
Potential reduce by 64 B
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. Living-in.eu has all CSS files already compressed.
Number of requests can be reduced by 4 (10%)
41
37
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Living In. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
living-in.eu
441 ms
living-in.eu
5012 ms
js
125 ms
css_70gMXwtmZRDsE-J5iavE0jExWReMwdVwdKEt6jhEF2s.css
107 ms
css_Cd57Gqoc3xv2twQxg-0gTNOd1mTEGS0NTpnzc1O1daQ.css
407 ms
392016372
464 ms
387995821
462 ms
377819446
455 ms
js_1VUtCYnv8JuQ3pJ1PPbcSw7vOtt9vcqLXr465q8Q9FU.js
1462 ms
living-in-eu.png
1963 ms
header_portraits.jpg
1961 ms
Huna%20marchio%20esploso%201000x413.png
907 ms
urban-data-platform.jpg
815 ms
sedum.png
2032 ms
city-bulding-digital.jpg
908 ms
AI.jpg
2030 ms
Enoll%20Logo.png
2061 ms
SDGs_Banner.png
2296 ms
info%20day_visual%2016x9.jpg
2035 ms
scrum-board.jpg
2035 ms
Eurocities-Logo-Pos-RGB.png
2084 ms
OASC_LOGO.jpg
2064 ms
european%20living%20labs.png
2063 ms
European_Commission.png
2078 ms
logo_european_committee_of_the_regions.png
2289 ms
join-boost-sustain.png
2667 ms
analytics.js
30 ms
collect
290 ms
837989905-a90565ab243b536c285ddb5a0ecd6e29b88bc4fa8a0483c0ff79055ea96d8d82-d.jpg
471 ms
player.js
668 ms
player.css
598 ms
vuid.min.js
557 ms
852254782-2bd17dc5845b6d49f5f4f1b082966d931d2fc3cf763edf21179df0b09411bcb2-d.jpg
398 ms
863268830-f2a351ecfd267a311526076250fd63bef63a410233e8fb4e855152a38a3ecc68-d.jpg
398 ms
heart.svg
1847 ms
collect
402 ms
OpenSans-Regular.woff
1639 ms
OpenSans-CondLight.woff
1880 ms
OpenSans-Light.woff
1878 ms
OpenSans-Semibold.woff
1878 ms
OpenSans-CondBold.woff
1877 ms
OpenSans-Bold.woff
1878 ms
OpenSans-ExtraBold.woff
1945 ms
SourceSerifPro-Regular.woff
2021 ms
SourceSerifPro-Light.woff
2020 ms
SourceSerifPro-ExtraLight.woff
2120 ms
SourceSerifPro-Semibold.woff
2166 ms
SourceSerifPro-Bold.woff
2664 ms
SourceSerifPro-Black.woff
2074 ms
fa-brands-400.woff
2167 ms
fa-solid-900.woff
2166 ms
fa-regular-400.woff
2167 ms
fa-light-300.woff
2666 ms
livingineu.woff
2520 ms
SourceSerifPro-It.woff
2439 ms
SourceSerifPro-LightIt.woff
2438 ms
vuid
962 ms
852254782-2bd17dc5845b6d49f5f4f1b082966d931d2fc3cf763edf21179df0b09411bcb2-d
644 ms
player-test-impression
579 ms
player-test-impression
442 ms
837989905-a90565ab243b536c285ddb5a0ecd6e29b88bc4fa8a0483c0ff79055ea96d8d82-d
2 ms
392016372
4 ms
387995821
3 ms
377819446
2 ms
392016372
3 ms
387995821
2 ms
377819446
2 ms
392016372
225 ms
387995821
370 ms
377819446
387 ms
SourceSerifPro-ExtraLightIt.woff
1389 ms
SourceSerifPro-SemiboldIt.woff
1387 ms
SourceSerifPro-BoldIt.woff
1362 ms
SourceSerifPro-BlackIt.woff
1319 ms
header_portraits.jpg
1376 ms
863268830-f2a351ecfd267a311526076250fd63bef63a410233e8fb4e855152a38a3ecc68-d
92 ms
852254782-2bd17dc5845b6d49f5f4f1b082966d931d2fc3cf763edf21179df0b09411bcb2-d
129 ms
837989905-a90565ab243b536c285ddb5a0ecd6e29b88bc4fa8a0483c0ff79055ea96d8d82-d
795 ms
living-in.eu 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
[role] values are not valid
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
living-in.eu 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
living-in.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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Living-in.eu 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 Living-in.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.
living-in.eu
Open Graph data is detected on the main page of Living In. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: