6.6 sec in total
1.2 sec
5.2 sec
290 ms
Visit ilife.co.th now to see the best up-to-date ILife content and also check out these interesting facts you probably never knew about ilife.co.th
บริหารหมู่บ้านจัดสรร คอนโดมิเนียม บริหารอาคารสูง อาคารชุด ด้วยมาตรฐานที่เป็นสากล ทีมงานคุณภาพ เทคโนโลยีการให้บริการที่ทันสมัย
Visit ilife.co.thWe analyzed Ilife.co.th page load time and found that the first response time was 1.2 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ilife.co.th performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value16.0 s
0/100
25%
Value18.6 s
0/100
10%
Value100 ms
98/100
30%
Value0.098
90/100
15%
Value20.2 s
2/100
10%
1165 ms
10 ms
479 ms
278 ms
619 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 34% of them (21 requests) were addressed to the original Ilife.co.th, 31% (19 requests) were made to Static.xx.fbcdn.net and 25% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Ilife.co.th.
Page size can be reduced by 33.9 kB (5%)
742.3 kB
708.4 kB
In fact, the total size of Ilife.co.th main page is 742.3 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. 60% of websites need less resources to load. Images take 725.5 kB which makes up the majority of the site volume.
Potential reduce by 12.5 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 12.5 kB or 74% of the original size.
Potential reduce by 21.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. ILife images are well optimized though.
Number of requests can be reduced by 20 (33%)
60
40
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ILife. 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 from 4 to 1 for CSS and as a result speed up the page load time.
ilife.co.th
1165 ms
all.js
10 ms
likebox.php
479 ms
BG_Page.png
278 ms
iLife_Logo.png
619 ms
index_02.png
621 ms
iLife_Service.png
620 ms
iLife_Customer.png
622 ms
iLife_Profile.png
623 ms
iLife_Contact.png
622 ms
index_07.png
4010 ms
index_08.png
858 ms
index_09.png
858 ms
spacer.gif
859 ms
index_10.png
862 ms
index_11.png
1410 ms
index_12.png
1078 ms
index_13.png
1073 ms
index_14.png
1359 ms
index_15.png
1107 ms
index_16.png
1337 ms
index_17.png
1345 ms
index_18.png
1654 ms
109 ms
xd_arbiter.php
32 ms
xd_arbiter.php
41 ms
likebox.php
550 ms
kyEKgjk51ZE.css
23 ms
xgj7bXhJNEH.css
28 ms
q68gy-v_YMF.js
40 ms
FJmpeSpHpjS.js
38 ms
0wM5s1Khldu.js
82 ms
1bNoFZUdlYZ.js
86 ms
529148_583519031694738_1388783915_n.jpg
291 ms
1907588_676059849107322_2009671147_n.jpg
32 ms
12813958_162127080842824_6068159082180291255_n.jpg
211 ms
12342629_10201332300627053_7404677262706418746_n.jpg
63 ms
1555468_10200682462098817_413993898_n.jpg
233 ms
12507319_1061049960625197_3637214012705204044_n.jpg
211 ms
12647016_928398530542818_5840831296902396639_n.jpg
232 ms
wL6VQj7Ab77.png
20 ms
s7jcwEQH7Sx.png
19 ms
Czh0gDTFcBt.css
14 ms
N-k91nHCZS2.css
19 ms
njO1TPvGzoR.js
14 ms
1QuX41zDRrx.js
14 ms
Oagsvfb4VWi.js
13 ms
LTv6ZK-5zxz.js
48 ms
1FCa-btixu2.js
81 ms
529148_583519031694738_1388783915_n.jpg
164 ms
1972502_918213954891909_3155427271128115247_n.jpg
41 ms
11233491_907024999344138_9220225270105682403_n.jpg
68 ms
19228_899883660058272_387855527246464082_n.jpg
69 ms
11074164_899883680058270_8120384147250845408_n.jpg
41 ms
11065096_892888454091126_4424235790179371197_n.jpg
76 ms
11149520_882379848475320_2097308007796928502_n.jpg
41 ms
18623_882379871808651_4798079306018318746_n.jpg
470 ms
QDwYpIaRyfG.png
35 ms
K00K-UgnsKu.png
37 ms
I6-MnjEovm5.js
13 ms
pQrUxxo5oQp.js
13 ms
ilife.co.th accessibility score
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
Image elements do not have [alt] attributes
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
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
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.
ilife.co.th 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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
ilife.co.th SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
TH
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ilife.co.th can be misinterpreted by Google and other search engines. Our service has detected that Thai 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 Ilife.co.th main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ilife.co.th
Open Graph description is not detected on the main page of ILife. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: