29.4 sec in total
2.3 sec
26.3 sec
778 ms
Welcome to fj.189.cn homepage info - get ready to check Fj 189 best content for China right away, or after learning these important things about fj.189.cn
中国电信欢go网•福建(原福建中国电信网上营业厅)-在线销售数码通讯、套餐/靓号等产品、正品低价、品质保障。同时为用户提供充值缴费、宽带办理、费用查询、在线客服、及品牌专区等全方位的网上自助服务;中国电信——世界触手可及。
Visit fj.189.cnWe analyzed Fj.189.cn page load time and found that the first response time was 2.3 sec and then it took 27.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
fj.189.cn performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value8.2 s
2/100
25%
Value15.8 s
0/100
10%
Value3,090 ms
2/100
30%
Value0.082
94/100
15%
Value16.2 s
6/100
10%
2289 ms
2060 ms
1059 ms
1991 ms
641 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fj.189.cn, 53% (39 requests) were made to Image1.chinatelecom-ec.com and 33% (24 requests) were made to Image2.chinatelecom-ec.com. The less responsive or slowest element that took the longest time to load (13.9 sec) relates to the external source .
Page size can be reduced by 293.7 kB (19%)
1.6 MB
1.3 MB
In fact, the total size of Fj.189.cn main page is 1.6 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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 150.4 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 37.2 kB, which is 21% 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 150.4 kB or 86% of the original size.
Potential reduce by 56.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. Fj 189 images are well optimized though.
Potential reduce by 62.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 62.6 kB or 74% of the original size.
Potential reduce by 24.4 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. Fj.189.cn needs all CSS files to be minified and compressed as it can save up to 24.4 kB or 81% of the original size.
Number of requests can be reduced by 9 (13%)
70
61
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fj 189. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
fj.189.cn
2289 ms
fj
2060 ms
1059 ms
common_indexv2.css
1991 ms
index.html
641 ms
index.html
737 ms
grey.gif
1906 ms
logo.png
1919 ms
right.html
614 ms
fcb13d59-46fd-4413-a810-9e1708af33fb.png
1161 ms
af5d9952-3c3a-4cb6-b164-7517d6e75b04.png
1769 ms
6f3c92cd-7a18-46c0-9847-ebb759c7d406.png
1958 ms
3968b904-d7fd-4221-8d89-48064f8ec8ec.jpg
1958 ms
c4c02330-f082-408f-b251-3e2906a590cb.jpg
2368 ms
682852ed-811d-4314-9fb0-6ec9888612d4.png
2378 ms
79232a95-af72-4e63-a818-563b66b7e33e.png
2401 ms
56fedf28-7fd9-4ddf-9e3f-3d2483471cf0.png
2354 ms
9adb8287-4ee4-41b4-bb21-3de785365146.png
2444 ms
6c2ebefc-a4c3-4118-9808-d817689829e1.png
2514 ms
05b2f2db-b29e-4cd7-8b9c-b501b2a7bf58.png
2971 ms
032b3260-1c22-41ab-b098-59ac51f49b78.jpg
1153 ms
82cd5a8d-8871-49e8-a78b-7f7b92b616ea.png
1212 ms
472ebf73-9ec6-48a6-a998-7a773de4bc0b.png
1211 ms
60a08354-f50c-4cc4-a6f0-ae83bbbb9e19.png
1212 ms
b9a96bc4-4c93-4084-ba2e-259a178edba5.png
1124 ms
7aa79541-0bd6-4830-9933-4831fef2fa3b.jpg
4051 ms
a3497970-6b5b-4e7e-a362-857722ee0a75.jpg
4086 ms
ffbac7f3-3b3e-4d49-a4a5-4959263c51f9.jpg
4352 ms
a9500b6b-329e-4050-b4dd-38ace7858dd6.jpg
4072 ms
265a1ea7-0d5c-4858-b695-7a335c532118.jpg
4577 ms
ae5ea2e4-72e6-4f4f-aba7-b8e966328639.png
4046 ms
055e6dc4-d2aa-422d-9bcb-0a6e7631cbce.png
4913 ms
5bbe4f44-6fc9-40a6-a142-f757ffa77d17.png
4622 ms
4a9444c3-fae8-4f65-ad31-a846e7bd5d09.png
4668 ms
9845f2b3-b4fb-49d1-9b26-7afe6f0b9a75.jpg
3493 ms
487b817f-c2cb-4e44-8765-d679f0a7b6c1.jpg
1616 ms
2e16d19d-0e81-428f-ae50-bc71e90d7500.jpg
1640 ms
fe96f472-9d1e-4b95-918a-1d1d461ac6a3.png
2036 ms
f3079fa1-8d59-49cb-915a-4e53c1cca73a.png
2182 ms
cf4ff095-1477-4103-94a8-2b59257b3213.png
1644 ms
8856efd5-82b5-45a5-b011-b0844549e163.png
2179 ms
0ab8c0de-44c9-4024-ad64-12d36852dc40.png
3328 ms
title_01.png
4603 ms
650ffaf4-7cfb-473b-aabd-9a83c64600fd.png
2238 ms
e91f0350-f23f-4620-98bc-d0cd1b1cfddf.png
3047 ms
jquery-1.8.3.js
5266 ms
fisheye-iutil.min.js
5060 ms
loadScript_1.1.js
5034 ms
jquery-1.11.2.min.js
5258 ms
jquery.cookie.js
4919 ms
serchTip.js
5047 ms
ioc_01.gif
5208 ms
HOT.png
5292 ms
HOT.png
2317 ms
b9de8792-4fe6-4541-ad08-089c94cbc852.jpg
2311 ms
indexright.css
316 ms
sl.jpg
4246 ms
belt_bj.jpg
4142 ms
btn_left_img.png
4309 ms
icon-189-indexv2.png
1541 ms
fangda.js
810 ms
js_common_indexv2.js
775 ms
index.do
706 ms
v.js
898 ms
cdcd427b-8f80-4f57-9059-e2c12dbef14e.png
836 ms
bottom_bg_img.png
283 ms
22d413f2-7dc8-4732-804f-7b68c2d902dd.jpg
632 ms
cd93a6eb-2306-4167-b503-48f5792c0c60.jpg
884 ms
3ebcda6f-dd3e-4baf-b4f4-00f804be4f3b.jpg
890 ms
82615046-85ce-4742-ae17-858c9e21fcd6.jpg
2215 ms
561a124a-df98-420d-ae57-8d5128e76578.png
597 ms
74dc7794-22c4-48e3-8e94-2aba398ffe38.png
634 ms
ct189.js
13853 ms
fj.189.cn 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
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
fj.189.cn 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
fj.189.cn 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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fj.189.cn 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 Fj.189.cn 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.
fj.189.cn
Open Graph description is not detected on the main page of Fj 189. 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: