9.7 sec in total
450 ms
9 sec
249 ms
Visit ejfq.com now to see the best up-to-date EJFQ content for Hong Kong and also check out these interesting facts you probably never knew about ejfq.com
由《信報》EJFQ「信號」團隊獨家研發,運用市場大數據及將機構投資者使用的分析工具,轉化為簡單的圖表和功能,助散戶無論在升市、跌市,都能更快、更準地找出值博股,提高勝算!
Visit ejfq.comWe analyzed Ejfq.com page load time and found that the first response time was 450 ms and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ejfq.com performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value22.2 s
0/100
25%
Value15.6 s
0/100
10%
Value5,620 ms
0/100
30%
Value0.504
16/100
15%
Value19.5 s
2/100
10%
450 ms
2817 ms
443 ms
449 ms
666 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 90% of them (106 requests) were addressed to the original Ejfq.com, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Ejfq.com.
Page size can be reduced by 971.4 kB (67%)
1.5 MB
486.6 kB
In fact, the total size of Ejfq.com main page is 1.5 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. 45% of websites need less resources to load. Javascripts take 898.1 kB which makes up the majority of the site volume.
Potential reduce by 47.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 47.5 kB or 80% of the original size.
Potential reduce by 10.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. EJFQ images are well optimized though.
Potential reduce by 620.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 620.6 kB or 69% of the original size.
Potential reduce by 292.7 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. Ejfq.com needs all CSS files to be minified and compressed as it can save up to 292.7 kB or 82% of the original size.
Number of requests can be reduced by 86 (75%)
114
28
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EJFQ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
ejfq.com
450 ms
landing.htm
2817 ms
fq_global.css
443 ms
fq_style.css
449 ms
fq_menu.css
666 ms
fq_stockq.css
430 ms
fq_search.css
454 ms
fq_trackersignal.css
867 ms
fq_footer.css
890 ms
fq_promote.css
889 ms
fq_global_tablesorter.css
681 ms
jquery.autocomplete.css
1105 ms
jquery.tooltip.css
1122 ms
jquery-ui.css
1967 ms
helpExtender.css
1329 ms
jquery.bxslider.css
1311 ms
jquery.js
1971 ms
jquery-ui.js
4756 ms
jquery.cookie.js
1759 ms
jquery-migrate.js
1741 ms
jquery.blockUI.js
1994 ms
jquery.bxslider.js
2626 ms
jquery.scrollTo.js
2188 ms
jquery.helpExtender.js
2397 ms
jquery.autocomplete.js
2422 ms
jquery.tooltip.js
2439 ms
jquery.qtip.js
2851 ms
dropdowncontent.js
2626 ms
function.js
3063 ms
browser.js
2871 ms
global_props.js
3052 ms
jquery.hkejLib.js
3053 ms
jquery.hkejFormLib.js
3279 ms
skeleton_head.js
3320 ms
fq_landing_forex.css
3281 ms
landing_tracker.js
3484 ms
research_landing.css
3073 ms
landing_topmid_specialbanner.css
2658 ms
thickbox.css
2653 ms
fq_landing_top10.css
2677 ms
fq_landing_onews.css
2677 ms
fq_news.css
2898 ms
fq_landing_industchart.css
2614 ms
fq_trackersignal.css
2427 ms
jquery.tooltip.css
2408 ms
thickbox.js
2411 ms
fq_landing_indexchart.css
2196 ms
fq_landing_portfo.css
2186 ms
landing_news.js
1999 ms
tracker_signal.js
2011 ms
landing_top10.js
2426 ms
landing_top10.js
1583 ms
jquery.tooltip.js
1570 ms
megahub_indexchart.js
1791 ms
landing_portfolio.js
1350 ms
analytics.js
21 ms
gtm.js
52 ms
toplogobar_bg.png
17 ms
stock_searchJQ.htm
451 ms
logo_ejfq112.png
11 ms
btn_login0.png
451 ms
btn_directpurhase0.png
219 ms
btn_howtouse0.png
460 ms
facebk_icon.jpg
14 ms
hkej_icon1.jpg
45 ms
fg_menutagbg_2w.png
45 ms
home_img_free.jpg
35 ms
ra_ad347x60.jpg
36 ms
specialbanner_chart201303c.jpg
38 ms
tracker_2.gif
36 ms
tracker_strength_basic.gif
36 ms
tracker_strength_changes_g0.gif
37 ms
tracker_0.gif
38 ms
tracker_1.gif
43 ms
sectorchange.png
477 ms
arrow_size1_up.gif
61 ms
arrow_size1_dn.gif
71 ms
but_morevid.jpg
78 ms
megalogo_small.gif
93 ms
fq_menubar_bg.jpg
91 ms
fg_menutagbg_4w.jpg
119 ms
fq_tdbg1.jpg
119 ms
collect
12 ms
fg_titlebar_bg.jpg
96 ms
collect
15 ms
fg_menutagbg_6w.jpg
89 ms
fg_menutagbg_5w.jpg
101 ms
videooptionbg.jpg
123 ms
tag_buttonbg3.jpg
128 ms
fg_listitembg.jpg
140 ms
fg_login_bg.jpg
118 ms
fq_submitbuttonbg.jpg
121 ms
indexchart.htm
602 ms
bx_loader.gif
99 ms
controls.png
111 ms
fq_loading.gif
104 ms
0sXBezTngi4
113 ms
www-embed-player-vflZsBgOl.css
69 ms
www-embed-player.js
92 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
38 ms
ad_status.js
37 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
76 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
85 ms
fq_global.css
669 ms
fq_stockq.css
5 ms
fq_style.css
449 ms
jquery.autocomplete.css
9 ms
jquery.js
22 ms
jquery.cookie.js
22 ms
jquery.autocomplete.js
41 ms
jquery.hkejLib.js
28 ms
skeleton_head.js
32 ms
megahub_recent_search_content.js
35 ms
EJFQOneDayChartServlet
940 ms
fg_indexchart_bg.jpg
6 ms
stockq_titlebar_bg.jpg
13 ms
stockq_contentbar_bg.jpg
7 ms
stockq_button2w_bg.jpg
5 ms
ejfq.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
ejfq.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
ejfq.com SEO score
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ejfq.com 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 Ejfq.com 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.
ejfq.com
Open Graph description is not detected on the main page of EJFQ. 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: