59.5 sec in total
4 sec
53.4 sec
2.1 sec
Welcome to yelites.org homepage info - get ready to check Yelites best content for Hong Kong right away, or after learning these important things about yelites.org
Visit yelites.orgWe analyzed Yelites.org page load time and found that the first response time was 4 sec and then it took 55.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
yelites.org performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value12.0 s
0/100
25%
Value12.1 s
4/100
10%
Value560 ms
53/100
30%
Value0.213
58/100
15%
Value10.0 s
26/100
10%
4015 ms
4942 ms
481 ms
775 ms
463 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 47% of them (41 requests) were addressed to the original Yelites.org, 26% (23 requests) were made to Static.xx.fbcdn.net and 21% (18 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (11.6 sec) belongs to the original domain Yelites.org.
Page size can be reduced by 951.8 kB (73%)
1.3 MB
352.8 kB
In fact, the total size of Yelites.org main page is 1.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. 40% of websites need less resources to load. Javascripts take 877.8 kB which makes up the majority of the site volume.
Potential reduce by 73.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. This page needs HTML code to be minified as it can gain 35.8 kB, which is 43% 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 73.1 kB or 88% of the original size.
Potential reduce by 60.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. Obviously, Yelites needs image optimization as it can save up to 60.4 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 697.3 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 697.3 kB or 79% of the original size.
Potential reduce by 121.0 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. Yelites.org needs all CSS files to be minified and compressed as it can save up to 121.0 kB or 86% of the original size.
Number of requests can be reduced by 41 (49%)
83
42
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yelites. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
4015 ms
jquery-1.8.2.min.js
4942 ms
pager.css
481 ms
jquery.pager_hk.js
775 ms
jquery.dropdownPlain.js
463 ms
style.css
486 ms
header.css
1961 ms
jquery.mousewheel-3.0.6.pack.js
794 ms
jquery.fancybox.js
1863 ms
jquery.fancybox.css
1116 ms
jquery.flexslider.js
2137 ms
flexslider.css
1355 ms
jquery.mmenu.min.all.js
2090 ms
jquery.mmenu.all.css
2328 ms
hamburger.css
2190 ms
jquery.ad-gallery.css
2324 ms
jquery.ad-gallery.js
2599 ms
boilerplate.css
2764 ms
index.css
2614 ms
jwplayer.js
1334 ms
jquery-ui.js
11648 ms
tabstyle.css
520 ms
jquery-ui.css
1801 ms
1792.png
1440 ms
search.jpg
253 ms
1797.jpg
4125 ms
1795.jpg
4240 ms
2258.jpg
3431 ms
2309.jpg
4130 ms
tab_facebook.png
1672 ms
tab_enews.png
1923 ms
sdk.js
314 ms
bg.jpg
4107 ms
calendar.php
3773 ms
2319.jpg
0 ms
2386.jpg
0 ms
294 ms
xd_arbiter.php
322 ms
xd_arbiter.php
549 ms
arrow_left.gif
1063 ms
arrow_right.gif
1065 ms
calendar.php
0 ms
ui-bg_glass_75_e6e6e6_1x400.png
568 ms
ui-bg_glass_65_ffffff_1x400.png
577 ms
flexslider-icon.woff
746 ms
page.php
393 ms
UM6GQR3fhLA.css
146 ms
wDWdtKDMSsA.css
172 ms
_LJpKKX4OAf.css
197 ms
haVjXmh8926.css
218 ms
Bgb3zaRkOok.css
246 ms
SRSW8M763HA.js
820 ms
BNt3DGF6TwA.js
454 ms
XokP-R2tSzH.js
336 ms
cTsUJN-URQ2.js
252 ms
RFvRVBkbFtO.js
476 ms
CRcwa2tmVNr.js
331 ms
PQJ3IcWl-DX.js
408 ms
UlhmM0m3TH8.js
394 ms
MYVAUMwx14D.js
396 ms
12417804_1550171051971730_4121791259776581886_n.jpg
273 ms
11143318_1412610425727794_7146896554509310013_n.jpg
317 ms
10690027_366872130131172_8085571130861143054_n.jpg
341 ms
12247175_10207832890965923_5245794431656003548_n.jpg
340 ms
1452111_10152036775191215_1036193337_n.jpg
348 ms
12523202_10207233056739236_5129329712442100836_n.jpg
343 ms
11866400_10206821252906158_578977881946749361_n.jpg
476 ms
10401495_734953323233020_2336701216048244099_n.jpg
369 ms
12963710_1054644287947457_1271868040531288931_n.jpg
429 ms
1391973_10152397249136231_6395112141183083168_n.jpg
424 ms
12938267_1604197643235737_8894285683673700878_n.jpg
1007 ms
12931211_1052876961440070_3872439860056419937_n.jpg
577 ms
12512791_1052875948106838_7910735128374772749_n.jpg
560 ms
12919687_1052875941440172_9075846729261156884_n.jpg
559 ms
11142426_1052875918106841_452227785025727985_n.jpg
544 ms
11140053_639789942835755_4498369770725572796_n.jpg
597 ms
12496725_639758736172209_54038157_n.jpg
720 ms
12594076_639420132872736_1934467128_n.jpg
745 ms
wL6VQj7Ab77.png
79 ms
Wh-wXqXludh.png
79 ms
bgs9JznbMav.png
77 ms
S4NGepoqhZB.js
77 ms
9TAncA0P76f.js
57 ms
R9GKCzjAnbk.js
9 ms
AWWjhOengNF.js
8 ms
YnSasnyq68i.js
11 ms
kQf_jlUv-kX.js
10 ms
yelites.org 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-hidden="true"] elements contain focusable descendents
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
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
yelites.org 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
yelites.org 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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yelites.org can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Yelites.org 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.
yelites.org
Open Graph description is not detected on the main page of Yelites. 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: