5.5 sec in total
184 ms
4.9 sec
420 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 184 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
living-in.eu performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value2.9 s
81/100
25%
Value6.7 s
36/100
10%
Value90 ms
99/100
30%
Value0.119
85/100
15%
Value8.0 s
42/100
10%
184 ms
1898 ms
526 ms
250 ms
243 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 99% of them (133 requests) were addressed to the original Living-in.eu, 1% (1 request) were made to Analytics.living-in.eu and 1% (1 request) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Living-in.eu.
Page size can be reduced by 180.6 kB (13%)
1.4 MB
1.2 MB
In fact, the total size of Living-in.eu main page is 1.4 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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 44.1 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 44.1 kB or 80% of the original size.
Potential reduce by 84.6 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 42.7 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 42.7 kB or 23% of the original size.
Potential reduce by 9.1 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. Living-in.eu needs all CSS files to be minified and compressed as it can save up to 9.1 kB or 19% of the original size.
Number of requests can be reduced by 91 (81%)
113
22
The browser has sent 113 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 56 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.
living-in.eu
184 ms
living-in.eu
1898 ms
matomo.js
526 ms
tracker.js
250 ms
slick.css
243 ms
slick.module.css
244 ms
ajax-progress.module.css
266 ms
align.module.css
265 ms
autocomplete-loading.module.css
266 ms
fieldgroup.module.css
324 ms
container-inline.module.css
326 ms
clearfix.module.css
334 ms
details.module.css
339 ms
hidden.module.css
339 ms
item-list.module.css
350 ms
js.module.css
405 ms
nowrap.module.css
407 ms
position-container.module.css
419 ms
progress.module.css
423 ms
reset-appearance.module.css
424 ms
resize.module.css
434 ms
sticky-header.module.css
485 ms
system-status-counter.css
488 ms
system-status-report-counters.css
503 ms
system-status-report-general-info.css
505 ms
tabledrag.module.css
507 ms
tablesort.module.css
521 ms
tree-child.module.css
565 ms
footnotes.css
568 ms
filter.caption.css
587 ms
filter.caption.css
589 ms
views.module.css
590 ms
blazy.css
603 ms
blazy.loading.css
646 ms
ucdashboard.css
649 ms
bootstrap-icons.css
16 ms
paragraphs.unpublished.css
670 ms
flag-link-ajax.css
673 ms
flag-link.css
674 ms
fonts.css
704 ms
style.css
575 ms
blazy.polyfill.min.js
497 ms
jquery.min.js
506 ms
element.matches.js
538 ms
object.assign.js
540 ms
nodelist.foreach.js
625 ms
css.escape.js
566 ms
es6-promise.auto.min.js
565 ms
blazy.classlist.min.js
559 ms
blazy.promise.min.js
555 ms
blazy.raf.min.js
558 ms
once.min.js
553 ms
jquery.once.min.js
537 ms
drupalSettingsLoader.js
545 ms
drupal.js
555 ms
drupal.init.js
556 ms
debounce.js
560 ms
picturefill.min.js
559 ms
dblazy.min.js
545 ms
blazy.dataset.min.js
549 ms
blazy.viewport.min.js
559 ms
blazy.dom.min.js
559 ms
blazy.xlazy.min.js
553 ms
blazy.observer.min.js
545 ms
blazy.loading.min.js
545 ms
blazy.webp.min.js
554 ms
blazy.base.min.js
554 ms
blazy.min.js
557 ms
bio.min.js
560 ms
slick.min.js
546 ms
bio.media.min.js
550 ms
blazy.drupal.min.js
559 ms
blazy.load.min.js
551 ms
blazy.compat.min.js
558 ms
index.umd.min.js
555 ms
matomo.js
505 ms
jquery.once.bc.js
521 ms
navigation.js
519 ms
mobile-navigation.js
513 ms
compact-label.js
517 ms
scrolled.js
437 ms
scrollto.js
439 ms
collapsible.js
485 ms
messageclose.js
509 ms
highchart-imp.js
506 ms
progress.js
511 ms
loadjs.min.js
514 ms
responsive_image.ajax.js
511 ms
ajax.js
521 ms
bio.ajax.min.js
525 ms
jquery.form.min.js
511 ms
base.js
505 ms
ajax_view.js
504 ms
flag-action_link_flash.js
504 ms
slick.load.min.js
514 ms
OpenSans-Regular.woff
621 ms
OpenSans-CondLight.woff
599 ms
OpenSans-Light.woff
598 ms
OpenSans-Semibold.woff
606 ms
OpenSans-CondBold.woff
605 ms
OpenSans-Bold.woff
548 ms
OpenSans-ExtraBold.woff
537 ms
SourceSerifPro-Regular.woff
673 ms
SourceSerifPro-Light.woff
691 ms
SourceSerifPro-ExtraLight.woff
659 ms
SourceSerifPro-Semibold.woff
733 ms
SourceSerifPro-Bold.woff
725 ms
SourceSerifPro-Black.woff
713 ms
fa-brands-400.woff
681 ms
fa-solid-900.woff
746 ms
fa-regular-400.woff
1168 ms
fa-light-300.woff
1160 ms
Bebas.woff
1112 ms
living-in-eu.png
1107 ms
read.svg
1087 ms
sign-round.svg
1081 ms
support-round.svg
1081 ms
register-member.svg
1079 ms
lot-1ldt-banner.png
1032 ms
screenshot-193.png
1015 ms
banner.png
1009 ms
screenshot-2024-01-29-at-16.28.44.png
1007 ms
header_portraits.jpg
1003 ms
Eurocities-Logo-Pos-RGB.png
999 ms
logo-ccre-cemr.png
949 ms
logo-errin.png
935 ms
OASC_LOGO.jpg
925 ms
european%20living%20labs.png
926 ms
European_Commission.png
918 ms
logo_european_committee_of_the_regions.png
916 ms
en-funded-by-the-eu-pos-very-small.jpg
757 ms
_track
1199 ms
heart.svg
755 ms
header_portraits.jpg
782 ms
_track
1195 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
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
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
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
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: