Tools & Wizards About Us
feeyo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

feeyo.com

航班动态

Page Load Speed

40.4 sec in total

First Response

7.5 sec

Resources Loaded

32.7 sec

Page Rendered

199 ms

feeyo.com screenshot

About Website

Visit feeyo.com now to see the best up-to-date Feeyo content for China and also check out these interesting facts you probably never knew about feeyo.com

飞常准（Variflight.com）属于飞友科技公司，是全球领先的航班数据服务公司, 帮飞行旅客提供跟踪航班动态查询航班状态、延误智能预报、航班点评等专业性功能，为携程去哪儿途牛同程春秋航空机票购买用户提供航班行程查询，为商旅用户提供贴心便捷的旅行服务，为机场、空管提供ACDM，保障航班正常

Visit feeyo.com

Key Findings

We analyzed Feeyo.com page load time and found that the first response time was 7.5 sec and then it took 32.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.

Performance Metrics

feeyo.com performance score

0

Network Requests Diagram

www.feeyo.com

7524 ms

autocomplete.css

433 ms

freedownload.css

757 ms

jquery.v1.7.min.js

4291 ms

commonfunction.js

438 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 30% of them (24 requests) were addressed to the original Feeyo.com, 54% (43 requests) were made to Cdn.feeyo.com and 4% (3 requests) were made to Carnoc.com. The less responsive or slowest element that took the longest time to load (15.7 sec) relates to the external source Fw.qq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 720.4 kB (44%)

Content Size

1.6 MB

After Optimization

926.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Feeyo.com 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. 25% of websites need less resources to load. Images take 755.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 60.3 kB

  • Original 74.8 kB
  • After minification 71.0 kB
  • After compression 14.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. 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 60.3 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 29.0 kB

  • Original 755.2 kB
  • After minification 726.3 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. Feeyo images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 296.1 kB

  • Original 426.4 kB
  • After minification 417.0 kB
  • After compression 130.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 296.1 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 335.0 kB

  • Original 390.9 kB
  • After minification 343.6 kB
  • After compression 55.8 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. Feeyo.com needs all CSS files to be minified and compressed as it can save up to 335.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (62%)

Requests Now

77

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Feeyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.feeyo.com

www.feeyo.com

7524 ms

autocomplete.css

autocomplete.css

433 ms

freedownload.css

freedownload.css

757 ms

jquery.v1.7.min.js

jquery.v1.7.min.js

4291 ms

commonfunction.js

commonfunction.js

438 ms

ServiceLocalCity.js

ServiceLocalCity.js

437 ms

newCalendar.js

newCalendar.js

432 ms

autocomplete.js

autocomplete.js

433 ms

WdatePicker.js

WdatePicker.js

2807 ms

train.js

train.js

433 ms

CityList.js

CityList.js

443 ms

default.css

default.css

1846 ms

tabs.js

tabs.js

1330 ms

welcome.js

welcome.js

433 ms

FPTS2_2013.js

FPTS2_2013.js

596 ms

SlideTrans.js

SlideTrans.js

2876 ms

pub_left_tonggao.js

pub_left_tonggao.js

1923 ms

is.asp

is.asp

2100 ms

Feeyo02.js

Feeyo02.js

407 ms

FPRS2_1.js

FPRS2_1.js

407 ms

dc.js

dc.js

2202 ms

freedl.js

freedl.js

3190 ms

businessLicense.js

businessLicense.js

4212 ms

urchin.js

urchin.js

11 ms

IndexMarqueeflightScreen_v2.js

IndexMarqueeflightScreen_v2.js

239 ms

WdatePicker.css

WdatePicker.css

569 ms

ListClose.gif

ListClose.gif

16 ms

1.jpg

1.jpg

59 ms

1.jpg

1.jpg

118 ms

iphonefree.gif

iphonefree.gif

861 ms

android.gif

android.gif

1231 ms

ipadfree.gif

ipadfree.gif

1282 ms

iphone.gif

iphone.gif

1155 ms

wp.gif

wp.gif

3968 ms

ipad.gif

ipad.gif

1266 ms

beian.png

beian.png

10331 ms

q.png

q.png

13 ms

top2.jpg

top2.jpg

14 ms

atop_new.gif

atop_new.gif

16 ms

tag2.gif

tag2.gif

18 ms

ico_n1.gif

ico_n1.gif

14 ms

ico_n2.gif

ico_n2.gif

16 ms

ico_n4.gif

ico_n4.gif

16 ms

ico_train.gif

ico_train.gif

16 ms

ico_n6.gif

ico_n6.gif

16 ms

ico_n8.gif

ico_n8.gif

17 ms

ico_n10.gif

ico_n10.gif

29 ms

ico_n11.gif

ico_n11.gif

25 ms

ico_n12.gif

ico_n12.gif

25 ms

tag3.gif

tag3.gif

26 ms

ico_n13.gif

ico_n13.gif

27 ms

ico_n14.gif

ico_n14.gif

27 ms

ico_n16.gif

ico_n16.gif

28 ms

ico_n17.gif

ico_n17.gif

28 ms

ico_n29.gif

ico_n29.gif

28 ms

ico_n30.gif

ico_n30.gif

30 ms

tag4.gif

tag4.gif

30 ms

ico_n25.gif

ico_n25.gif

27 ms

ico_n26.gif

ico_n26.gif

31 ms

wx.jpg

wx.jpg

30 ms

veryzhun_sina.jpg

veryzhun_sina.jpg

28 ms

v.jpg

v.jpg

46 ms

jiawx.jpg

jiawx.jpg

46 ms

bg.jpg

bg.jpg

45 ms

logo.gif

logo.gif

39 ms

calendar.htm

calendar.htm

1755 ms

datePicker.gif

datePicker.gif

3134 ms

Search.gif

Search.gif

28 ms

13071805005859.jpg

13071805005859.jpg

8594 ms

laba.gif

laba.gif

66 ms

dc_01.js

dc_01.js

3143 ms

show_feeyo.js

show_feeyo.js

1790 ms

dc_02.js

dc_02.js

2262 ms

next.gif

next.gif

7 ms

rtitleico.png

rtitleico.png

8 ms

Ei!readEiImgByMemory.action

Ei!readEiImgByMemory.action

1921 ms

__utm.gif

__utm.gif

8 ms

hm.js

hm.js

1394 ms

ipaddress

ipaddress

15733 ms

PEK_new.js

PEK_new.js

3009 ms

SEO Factors

feeyo.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Feeyo.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 Feeyo.com main page’s claimed encoding is gb2312. 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.

Social Sharing Optimization

feeyo.com

Open Graph description is not detected on the main page of Feeyo. 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: