2.1 sec in total
167 ms
1.7 sec
272 ms
Welcome to ilost.co homepage info - get ready to check ILost best content for Netherlands right away, or after learning these important things about ilost.co
Searching, reporting, matching. One in three found objects is returned to its owner via iLost, wherever in the world they live.
Visit ilost.coWe analyzed Ilost.co page load time and found that the first response time was 167 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
ilost.co performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value6.5 s
9/100
25%
Value3.2 s
91/100
10%
Value360 ms
72/100
30%
Value0.571
12/100
15%
Value7.3 s
50/100
10%
167 ms
389 ms
77 ms
82 ms
154 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 52% of them (32 requests) were addressed to the original Ilost.co, 10% (6 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (793 ms) belongs to the original domain Ilost.co.
Page size can be reduced by 632.0 kB (69%)
913.8 kB
281.7 kB
In fact, the total size of Ilost.co main page is 913.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. 50% of websites need less resources to load. Javascripts take 635.9 kB which makes up the majority of the site volume.
Potential reduce by 21.8 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 3.3 kB, which is 11% 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 21.8 kB or 75% 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. ILost images are well optimized though.
Potential reduce by 407.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 407.6 kB or 64% of the original size.
Potential reduce by 202.6 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. Ilost.co needs all CSS files to be minified and compressed as it can save up to 202.6 kB or 83% of the original size.
Number of requests can be reduced by 23 (45%)
51
28
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ILost. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
ilost.co
167 ms
ilost.co
389 ms
css
77 ms
jquery.min.js
82 ms
340665043.js
154 ms
application.css
182 ms
bower.js
461 ms
application.js
277 ms
messages_en.js
278 ms
gtm.js
85 ms
badge_light.png
160 ms
ilost_logo@2x.png
105 ms
header@2x.jpg
572 ms
iphone.png
222 ms
apple_store.png
382 ms
google_play.png
382 ms
syntus.jpg
377 ms
rijks_museum.jpg
378 ms
pathe.png
380 ms
awakenings.png
381 ms
hertz.png
403 ms
rai_amsterdam.png
403 ms
walibi_holland.jpg
438 ms
gemeente_nijmegen.png
529 ms
jaarbeurs.png
474 ms
dolfinarium.jpg
487 ms
volkshotel.jpg
479 ms
gemeente_ermelo.png
774 ms
gemeente_hilversum.jpg
560 ms
van_der_valk.jpg
569 ms
amsterdam-arena.jpg
568 ms
twitter.png
774 ms
facebook.png
775 ms
googleplus.png
786 ms
instagram.png
784 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
47 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
55 ms
fontawesome-webfont.woff
793 ms
zhcz-_WihjSQC0oHJ9TCYMDdSZkkecOE1hvV7ZHvhyU.ttf
96 ms
IQHow_FEYlDC4Gzy_m8fcsBaWKZ57bY3RXgXH6dOjZ0.ttf
97 ms
hotjar-30176.js
310 ms
analytics.js
42 ms
567396.js
300 ms
collect
18 ms
collect
61 ms
mixpanel-2-latest.min.js
65 ms
bugsnag-2.min.js
85 ms
iframe_api
90 ms
ajax-loader.gif
413 ms
29 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
42 ms
widgets.js
128 ms
www-widgetapi.js
61 ms
c2tyiOhsr2Y
80 ms
www-embed-player-vflfNyN_r.css
35 ms
www-embed-player.js
19 ms
base.js
86 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
82 ms
ad_status.js
49 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
21 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
22 ms
__ptq.gif
30 ms
ilost.co 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role] values are not valid
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
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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ilost.co 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
ilost.co 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
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 Ilost.co 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 Ilost.co 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.
ilost.co
Open Graph data is detected on the main page of ILost. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: