Tools & Wizards About Us
dage.cc screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

dage.cc

国际永久地址

Page Load Speed

63.7 sec in total

First Response

6.6 sec

Resources Loaded

56.1 sec

Page Rendered

981 ms

dage.cc screenshot

About Website

Welcome to dage.cc homepage info - get ready to check Dage best content for China right away, or after learning these important things about dage.cc

222。

Visit dage.cc

Key Findings

We analyzed Dage.cc page load time and found that the first response time was 6.6 sec and then it took 57.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. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

dage.cc performance score

0

Network Requests Diagram

dage.cc

6634 ms

base.css

347 ms

jquery-1.8.2.min.js

947 ms

base.js

412 ms

log.js

570 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 11% of them (14 requests) were addressed to the original Dage.cc, 35% (43 requests) were made to Images.dage.cc and 10% (13 requests) were made to Cqpcyzs.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Stat.funshion.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 654.2 kB (12%)

Content Size

5.2 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dage.cc main page is 5.2 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 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 98.6 kB

  • Original 118.9 kB
  • After minification 99.6 kB
  • After compression 20.3 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 19.3 kB, which is 16% 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 98.6 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 284.8 kB

  • Original 4.7 MB
  • After minification 4.4 MB

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. Dage images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 245.1 kB

  • Original 394.5 kB
  • After minification 388.6 kB
  • After compression 149.4 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 245.1 kB or 62% of the original size.

CSS Optimization

-77%

Potential reduce by 25.7 kB

  • Original 33.6 kB
  • After minification 28.8 kB
  • After compression 7.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. Dage.cc needs all CSS files to be minified and compressed as it can save up to 25.7 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (34%)

Requests Now

118

After Optimization

78

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dage.cc

dage.cc

6634 ms

base.css

base.css

347 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

947 ms

base.js

base.js

412 ms

log.js

log.js

570 ms

2016432046158321.jpg

2016432046158321.jpg

1747 ms

bg.png

bg.png

199 ms

banner.jpg

banner.jpg

368 ms

logo.gif

logo.gif

173 ms

search-button.gif

search-button.gif

184 ms

nav-line.gif

nav-line.gif

201 ms

nav-arrow.gif

nav-arrow.gif

358 ms

looked-arrow.gif

looked-arrow.gif

368 ms

46931.jpg

46931.jpg

363 ms

2014120274794516.jpg

2014120274794516.jpg

1256 ms

20162192219636752.jpg

20162192219636752.jpg

1835 ms

201622511392548233.jpg

201622511392548233.jpg

1672 ms

201631714461289283.jpg

201631714461289283.jpg

1694 ms

201631623221918796.jpg

201631623221918796.jpg

1813 ms

201632123161290808.jpg

201632123161290808.jpg

1775 ms

201581717232764133.jpg

201581717232764133.jpg

1849 ms

20151213025076390.jpg

20151213025076390.jpg

1885 ms

201510920461452706.jpg

201510920461452706.jpg

2109 ms

201612311115314322.jpg

201612311115314322.jpg

2125 ms

201512114534713496.jpg

201512114534713496.jpg

2216 ms

201151215244761576.jpg

201151215244761576.jpg

2012 ms

20161310561966717.jpg

20161310561966717.jpg

2278 ms

20162413374999716.jpg

20162413374999716.jpg

2291 ms

20157310491897290.jpg

20157310491897290.jpg

2412 ms

20162917384269739.jpg

20162917384269739.jpg

2445 ms

201312212253971974.jpg

201312212253971974.jpg

2317 ms

20092121335723210.jpg

20092121335723210.jpg

2434 ms

2014122516232428703.jpg

2014122516232428703.jpg

2676 ms

20161922204455820.jpg

20161922204455820.jpg

2593 ms

2013122121505536568.jpg

2013122121505536568.jpg

2517 ms

20144115245512279.jpg

20144115245512279.jpg

2775 ms

20144118472521229.jpg

20144118472521229.jpg

2875 ms

201433010283823992.jpg

201433010283823992.jpg

2830 ms

2009041361238893.jpg

2009041361238893.jpg

2657 ms

2009012411398547.jpg

2009012411398547.jpg

2705 ms

20142165192581523.jpg

20142165192581523.jpg

2833 ms

201571110481463177.jpg

201571110481463177.jpg

2867 ms

20153119422425351.jpg

20153119422425351.jpg

3092 ms

2014131512093542.jpg

2014131512093542.jpg

2980 ms

20161121131731921.jpg

20161121131731921.jpg

3168 ms

2015101619203992386.jpg

2015101619203992386.jpg

3006 ms

201611122271827196.jpg

201611122271827196.jpg

3074 ms

20159712245705.jpg

20159712245705.jpg

3302 ms

2015102011582247210.jpg

2015102011582247210.jpg

3246 ms

os.js

os.js

962 ms

ecvm

ecvm

960 ms

20159413581711650.jpg

20159413581711650.jpg

2176 ms

201412221692682453.jpg

201412221692682453.jpg

1604 ms

201522611241546797.jpg

201522611241546797.jpg

3151 ms

2014121923182297932.jpg

2014121923182297932.jpg

1609 ms

201417085435606.jpg

201417085435606.jpg

1764 ms

2015418154793899.jpg

2015418154793899.jpg

1732 ms

20146211584051526.jpg

20146211584051526.jpg

3170 ms

tuku.htm

tuku.htm

1057 ms

ecvm

ecvm

483 ms

6912_957.html

6912_957.html

1382 ms

star-min.gif

star-min.gif

194 ms

hm.js

hm.js

1666 ms

stat.php

stat.php

2271 ms

ecvm

ecvm

497 ms

00.png

00.png

1928 ms

20150520185433154.jpg

20150520185433154.jpg

3065 ms

2015052018533175.jpg

2015052018533175.jpg

852 ms

20150520185356100.jpg

20150520185356100.jpg

1837 ms

20150520185512240.jpg

20150520185512240.jpg

3777 ms

20150520185653582.jpg

20150520185653582.jpg

958 ms

201505201906402243.jpg

201505201906402243.jpg

1628 ms

201505201907382377.jpg

201505201907382377.jpg

1322 ms

201505201910422940.jpg

201505201910422940.jpg

1243 ms

201505201919434482.jpg

201505201919434482.jpg

1899 ms

201505201920594693.jpg

201505201920594693.jpg

2133 ms

2015052101101448103.jpg

2015052101101448103.jpg

2137 ms

201505201943327527.jpg

201505201943327527.jpg

2496 ms

getPosData0

getPosData0

2128 ms

hm.gif

hm.gif

435 ms

stat.htm

stat.htm

575 ms

core.php

core.php

1443 ms

960x90.jpg

960x90.jpg

1364 ms

dot.gif

dot.gif

1912 ms

9.gif

9.gif

1187 ms

cpv_dl.js

cpv_dl.js

1044 ms

sdl.ashx

sdl.ashx

11725 ms

app.gif

app.gif

2073 ms

sdl1.ashx

sdl1.ashx

6206 ms

tj.yule8.net

tj.yule8.net

925 ms

shell_v2.js

shell_v2.js

849 ms

logger.js

logger.js

430 ms

bds_s_v2.js

bds_s_v2.js

1692 ms

z_stat.php

z_stat.php

1596 ms

stat.htm

stat.htm

165 ms

core.php

core.php

279 ms

bdsstyle.css

bdsstyle.css

429 ms

l5.gif

l5.gif

433 ms

fx.htm

fx.htm

391 ms

Wno.html

Wno.html

11 ms

z_stat.php

z_stat.php

984 ms

z_stat.php

z_stat.php

1427 ms

stat.htm

stat.htm

170 ms

core.php

core.php

274 ms

stat.htm

stat.htm

177 ms

core.php

core.php

699 ms

index

index

678 ms

g-105488.v-265338

g-105488.v-265338

900 ms

close.png

close.png

453 ms

sdl2.ashx

sdl2.ashx

890 ms

logo.png

logo.png

2599 ms

statIwt_www_new-min.js

statIwt_www_new-min.js

1059 ms

baikal

baikal

20382 ms

vasd_pv.js

vasd_pv.js

9 ms

core-min.js

core-min.js

1047 ms

fun_vasd

fun_vasd

20372 ms

jiameng1.gif

jiameng1.gif

4837 ms

irt

irt

5860 ms

blank.gif

blank.gif

1588 ms

o.htm

o.htm

934 ms

hm.gif

hm.gif

897 ms

wh.js

wh.js

749 ms

ac.js

ac.js

565 ms

fp.htm

fp.htm

553 ms

SEO Factors

dage.cc 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 Dage.cc 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 Dage.cc 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

dage.cc

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