Tools & Wizards About Us
icross.cc screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

icross.cc

105學年度碩士班考試 | iCross - 愛交叉 - 研究所與大學交叉查榜系統

Page Load Speed

1.7 sec in total

First Response

213 ms

Resources Loaded

1.3 sec

Page Rendered

165 ms

icross.cc screenshot

About Website

Welcome to icross.cc homepage info - get ready to check ICross best content for Taiwan right away, or after learning these important things about icross.cc

iCross - 愛交叉,研究所與大學交叉查榜系統。 **目前 105 學年度最新的榜單已經上線囉。

Visit icross.cc

Key Findings

We analyzed Icross.cc page load time and found that the first response time was 213 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

icross.cc performance score

0

Network Requests Diagram

icross.cc

213 ms

application-eb2494b9448644e961cdfac71412fcb0.css

57 ms

application-23a73577954f20313c0d06ba590e1951.js

94 ms

ga.js

67 ms

all.js

42 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Icross.cc, 48% (25 requests) were made to Static.xx.fbcdn.net and 25% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (277 ms) relates to the external source Scontent.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 431.6 kB (65%)

Content Size

666.8 kB

After Optimization

235.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Icross.cc main page is 666.8 kB. 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. Javascripts take 277.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 31.4 kB

  • Original 40.3 kB
  • After minification 40.3 kB
  • After compression 8.8 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 31.4 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 2.8 kB

  • Original 93.4 kB
  • After minification 90.5 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. ICross images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 176.6 kB

  • Original 277.8 kB
  • After minification 277.8 kB
  • After compression 101.1 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 176.6 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 220.7 kB

  • Original 255.4 kB
  • After minification 253.7 kB
  • After compression 34.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. Icross.cc needs all CSS files to be minified and compressed as it can save up to 220.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (54%)

Requests Now

50

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

icross.cc

icross.cc

213 ms

application-eb2494b9448644e961cdfac71412fcb0.css

application-eb2494b9448644e961cdfac71412fcb0.css

57 ms

application-23a73577954f20313c0d06ba590e1951.js

application-23a73577954f20313c0d06ba590e1951.js

94 ms

ga.js

ga.js

67 ms

all.js

all.js

42 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

228 ms

29 ms

inpage_linkid.js

inpage_linkid.js

26 ms

xd_arbiter.php

xd_arbiter.php

34 ms

__utm.gif

__utm.gif

15 ms

ping

ping

34 ms

like.php

like.php

46 ms

like_box.php

like_box.php

229 ms

wy1X4hBW7e7.js

wy1X4hBW7e7.js

26 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

13 ms

4P2PlI2Xj1w.css

4P2PlI2Xj1w.css

9 ms

edHKvLIRWb_.css

edHKvLIRWb_.css

11 ms

D6bkeoC_tHV.css

D6bkeoC_tHV.css

19 ms

HdrCAJtTO8H.css

HdrCAJtTO8H.css

37 ms

lkgnQHMofcC.css

lkgnQHMofcC.css

27 ms

M9KHpdajqnb.css

M9KHpdajqnb.css

43 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

45 ms

ehA1CqzHyzE.js

ehA1CqzHyzE.js

64 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

18 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

44 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

79 ms

1QuX41zDRrx.js

1QuX41zDRrx.js

83 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

81 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

89 ms

1FCa-btixu2.js

1FCa-btixu2.js

81 ms

1916724_113858901959188_177843_n.jpg

1916724_113858901959188_177843_n.jpg

277 ms

safe_image.php

safe_image.php

194 ms

1425585_1052625378127594_167253099609141144_n.jpg

1425585_1052625378127594_167253099609141144_n.jpg

29 ms

946467_1091604130864296_5435175175082435434_n.jpg

946467_1091604130864296_5435175175082435434_n.jpg

44 ms

11951220_986271281393948_3083436939352694651_n.jpg

11951220_986271281393948_3083436939352694651_n.jpg

35 ms

11695763_1012204498803826_7050498592978571606_n.jpg

11695763_1012204498803826_7050498592978571606_n.jpg

31 ms

11986404_968446763177416_3293643710334553770_n.jpg

11986404_968446763177416_3293643710334553770_n.jpg

31 ms

164761_180126138683624_4293591_n.jpg

164761_180126138683624_4293591_n.jpg

32 ms

10314555_1005671366188443_3493068594238018181_n.jpg

10314555_1005671366188443_3493068594238018181_n.jpg

33 ms

11209348_865413080215801_2244540177561776741_n.jpg

11209348_865413080215801_2244540177561776741_n.jpg

36 ms

12314111_1073110029375450_5876145916287550858_n.jpg

12314111_1073110029375450_5876145916287550858_n.jpg

38 ms

12688217_1110467952298753_5762502577679260981_n.jpg

12688217_1110467952298753_5762502577679260981_n.jpg

36 ms

1979744_746087418736330_867236279_n.jpg

1979744_746087418736330_867236279_n.jpg

39 ms

995895_626587860686287_1442408586_n.jpg

995895_626587860686287_1442408586_n.jpg

158 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

22 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

23 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

22 ms

sSwLTfB7PfP.png

sSwLTfB7PfP.png

24 ms

K0srxReVLKP.png

K0srxReVLKP.png

24 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

24 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

6 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

6 ms

SEO Factors

icross.cc SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Icross.cc can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Icross.cc 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.

Social Sharing Optimization

icross.cc

Open Graph data is detected on the main page of ICross. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: