46.1 sec in total
2.2 sec
43.5 sec
398 ms
Click here to check amazing Flyertea content for China. Otherwise, check out these important facts you probably never knew about flyertea.com
FLYERT飞客,是全球常旅客交流最频繁的一个社交网站之一,更是中文常旅客网站中的佼佼者!在这里,来自全球的“飞客”们分享着最新鲜的酒店出游资讯、新店探店、入住体验、攻略福利、隐藏玩法,让每一次商务出行或休闲出游变得充满乐趣!
Visit flyertea.comWe analyzed Flyertea.com page load time and found that the first response time was 2.2 sec and then it took 43.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
flyertea.com performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value8.4 s
2/100
25%
Value12.3 s
3/100
10%
Value540 ms
55/100
30%
Value0
100/100
15%
Value9.3 s
31/100
10%
2230 ms
3330 ms
3204 ms
821 ms
5682 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 25% of them (39 requests) were addressed to the original Flyertea.com, 17% (27 requests) were made to Ptf.flyert.com and 7% (11 requests) were made to Pos.baidu.com. The less responsive or slowest element that took the longest time to load (18.9 sec) belongs to the original domain Flyertea.com.
Page size can be reduced by 787.8 kB (34%)
2.3 MB
1.6 MB
In fact, the total size of Flyertea.com main page is 2.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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 80.0 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 80.0 kB or 76% of the original size.
Potential reduce by 115.0 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. Flyertea images are well optimized though.
Potential reduce by 451.9 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 451.9 kB or 65% of the original size.
Potential reduce by 140.9 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. Flyertea.com needs all CSS files to be minified and compressed as it can save up to 140.9 kB or 80% of the original size.
Number of requests can be reduced by 46 (30%)
152
106
The browser has sent 152 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flyertea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
flyertea.com
2230 ms
index.php
3330 ms
style_41_common.css
3204 ms
style_41_portal_index.css
821 ms
common.js
5682 ms
jquery.min.js
5693 ms
m.js
828 ms
ds.js
1101 ms
portal.js
5686 ms
GB_BIG1.js
5292 ms
guide.css
2234 ms
xmSlide.js
4874 ms
responsiveslides.min.js
4876 ms
plugin.php
1712 ms
login19_blue.css
4865 ms
comiis.css
412 ms
comiis.js
829 ms
discuz_tips.js
492 ms
hm.js
742 ms
login_btn.png
1886 ms
qq_login.gif
25 ms
comiis_topbgico.gif
25 ms
logo.png
276 ms
u34.png
25 ms
ico_see.png
26 ms
112726xazh1tdfztyf3apa.jpg
28 ms
95_avatar_middle.jpg
26 ms
37_avatar_middle.jpg
32 ms
37_avatar_middle.jpg
28 ms
12_avatar_middle.jpg
29 ms
73_avatar_middle.jpg
30 ms
27_avatar_middle.jpg
29 ms
94_avatar_middle.jpg
33 ms
05_avatar_middle.jpg
32 ms
comiis_dmob.jpg
34 ms
comiis_dwx.jpg
33 ms
clifeisbetter.png
33 ms
e3f63b992a637e476f662b42682e5656.jpg
412 ms
2820502d331f8700d3429002e4fe715b.jpg
811 ms
f6d9e61f1e71d2fa679b78eb1d2358ad.jpg
413 ms
f50c87e7e7d05be077759358da05feef.jpg
410 ms
a55af0705258c49f7f597f1602aac804.jpg
1225 ms
2bc45960a7ad6bd1cc4eeae8dadefa9e.jpg
4030 ms
b9a25931c6f8fc496a970a7e7a50876a.jpg
2410 ms
eb30b98864f72a70caca5c0d5b59d2b7.jpg
2085 ms
0145ef468f33602953937a1e8333a926.jpg
3230 ms
369f5398099f12451fd18142f822146f.jpg
4178 ms
e8bbf405a270dc0410a49dbf5f64f044.jpg
6050 ms
26124ade4973ed52d0436d75aaa168ac.jpg
3366 ms
46e8e80ab2a0f3a2e6388bd7863b3b97.jpg
4112 ms
2ffc6f3d57aab9ba6918e0bc56ec1f74.jpg
12528 ms
1073e3ede79e73a104bda7967eb62b7b.jpg
4197 ms
1564ae1b217f3948427b1f259f339a47.jpg
5247 ms
f96665ae07ff8b0c0ff15d1bef027e0a.jpg
4974 ms
d09731ea814e8b6776d4a02b4218d708.jpg
5426 ms
b992988e0344c5f4950aeeeba86ad171.jpg
4609 ms
ebfc4ba429ae5750c96d7fd995b2ef58.jpg
5027 ms
173102h24uffnmjkf7om9m.jpg
18866 ms
19314c83e5f2a3ca104a266685f6aa15.jpg
6913 ms
219198a216e47b6a8d995a5d25c44614.jpg
5649 ms
2333b56a0728502f45ade2c883ccd5e5.jpg
6933 ms
3ddc6c6fa39f4c4ae9c65f5a886ea53f.jpg
7132 ms
a4d4d9113451e94079c1ee8d67c2ba81.jpg
7131 ms
comiis_close.gif
7331 ms
index.php
9419 ms
comiis_navssbg.gif
5 ms
arrwd.gif
14 ms
comiis_subbg.png
10 ms
gcqm
949 ms
hm.gif
360 ms
slide.js
482 ms
0f00025NI8QVXVCTLGbq8f.jpg
2604 ms
comiis_home_ico.gif
29 ms
0f000cglOPSO1Jp0xjo6Fs.jpg
2794 ms
0f0000-_p9TATzt0_VTKzs.jpg
1501 ms
0f000cglO2XO1Jp0xjo6Qs.jpg
3610 ms
0f000nNRGnl_G96xhKqE8f.jpg
1317 ms
comiis_ftbtn.png
25 ms
gcqm
503 ms
gcqm
475 ms
0f000Fj3MENNkBPqbbHnC6.jpg
1101 ms
gcqm
1939 ms
gcqm
489 ms
index.php
11829 ms
gcqm
511 ms
gcqm
4363 ms
weiboShow.css
40 ms
skin_default.css
40 ms
gaea_1_19.js
46 ms
wb_logo16_a.png
20 ms
1
41 ms
icon_user.png
19 ms
btns_bg.png
18 ms
icon_follow.png
19 ms
5b7c469agw1f2peb4fg3kg20a0060q8t.gif
115 ms
5b7c469agw1f2pdpusuesj20dw08cglu.jpg
56 ms
005A0thjgw1f2pclizmplj30sg0iz40a.jpg
31 ms
code.css
525 ms
jquery-1.8.2.min.js
615 ms
0f0000Qi7c044-MiP9WAl0.jpg
728 ms
close.gif
513 ms
gcqm
487 ms
h.js
374 ms
0f000F4M8IWfTQos0u_LY0.jpg
814 ms
view_icon.png
22 ms
comiis_ljt.gif
408 ms
comiis_dot.gif
405 ms
comiis_rjt.gif
411 ms
comiis_foot_ico.gif
7 ms
scrolltop.png
6 ms
gcqm
477 ms
21.gif
752 ms
hm.gif
373 ms
gcqm
484 ms
hm.gif
381 ms
5b7c469agw1f2p1dzzcy3j20m80tm0xk.jpg
28 ms
5b7c469agw1f2p17relosj20m80et455.jpg
241 ms
5b7c469agw1f2nvhcam7hj20m80gomyi.jpg
31 ms
5b7c469agw1f2mraonu7xj20m80godjh.jpg
16 ms
5b7c469agw1f2nyycesbfj20m80gojvy.jpg
43 ms
5b7c469agw1f2nvspkg3cj20m80ci77w.jpg
45 ms
5b7c469agw1f2mr36htk6j20m80dxgn1.jpg
39 ms
5b7c469agw1f2lk39uy05j20m80gotak.jpg
45 ms
5b7c469agw1f2n4c2jdc1j20rf0gltb5.jpg
34 ms
5b7c469agw1f2mrrzia65j20m80goae1.jpg
67 ms
5b7c469agw1f2n2mrs4eej20m80gotd4.jpg
32 ms
5b7c469agw1f2n221zb80j20le0egwhm.jpg
40 ms
5b7c469agw1f2mt1jvg07j20d50bw75u.jpg
33 ms
5b7c469agw1f2mrfyl2s9j20m80tnjtn.jpg
38 ms
1
973 ms
1
40 ms
0
19 ms
1
32 ms
suda.js
239 ms
0
21 ms
1
26 ms
1
25 ms
0
10 ms
0
9 ms
1
9 ms
0
11 ms
0
10 ms
1
14 ms
1
13 ms
1
966 ms
0
968 ms
0
979 ms
1
966 ms
1
968 ms
show.js
434 ms
bg_trans.png
9 ms
icon_tips.png
6 ms
a.gif
1059 ms
tmp.gif
10014 ms
o.htm
4951 ms
hm.gif
750 ms
wh.js
733 ms
ac.js
498 ms
flyertea.com accessibility score
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
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
Image elements do not have [alt] attributes
Links do not have a discernible 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
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.
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.
flyertea.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
flyertea.com 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
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flyertea.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 Flyertea.com main page’s claimed encoding is gbk. 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.
flyertea.com
Open Graph description is not detected on the main page of Flyertea. 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: