Tools & Wizards About Us
eeefff.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

eeefff.net

爱上家乡网，乡情乡音，顺风车拼车！便民信息综合平台！ - Powered by Discuz!

Page Load Speed

54.7 sec in total

First Response

16.3 sec

Resources Loaded

38.2 sec

Page Rendered

150 ms

eeefff.net screenshot

About Website

Click here to check amazing Eeefff content. Otherwise, check out these important facts you probably never knew about eeefff.net

爱上家乡网，乡情乡音，顺风车拼车！便民信息综合平台！

Visit eeefff.net

Key Findings

We analyzed Eeefff.net page load time and found that the first response time was 16.3 sec and then it took 38.4 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.

Performance Metrics

eeefff.net performance score

0

Network Requests Diagram

forum.php

16268 ms

style_1_common.css

1542 ms

style_1_forum_index.css

708 ms

common.js

1358 ms

style_1_widthauto.css

491 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 73% of them (35 requests) were addressed to the original Eeefff.net, 8% (4 requests) were made to Pub.idqqimg.com and 6% (3 requests) were made to Tcss.qq.com. The less responsive or slowest element that took the longest time to load (16.3 sec) belongs to the original domain Eeefff.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 158.7 kB (68%)

Content Size

235.1 kB

After Optimization

76.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eeefff.net main page is 235.1 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. Only 10% of websites need less resources to load. Javascripts take 115.0 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 14.5 kB

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 6.6 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 14.5 kB or 69% of the original size.

Image Optimization

-21%

Potential reduce by 4.7 kB

  • Original 22.7 kB
  • After minification 18.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. Obviously, Eeefff needs image optimization as it can save up to 4.7 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 80.4 kB

  • Original 115.0 kB
  • After minification 98.4 kB
  • After compression 34.7 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 80.4 kB or 70% of the original size.

CSS Optimization

-77%

Potential reduce by 59.2 kB

  • Original 76.4 kB
  • After minification 74.8 kB
  • After compression 17.2 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. Eeefff.net needs all CSS files to be minified and compressed as it can save up to 59.2 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (57%)

Requests Now

46

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forum.php

forum.php

16268 ms

style_1_common.css

style_1_common.css

1542 ms

style_1_forum_index.css

style_1_forum_index.css

708 ms

common.js

common.js

1358 ms

style_1_widthauto.css

style_1_widthauto.css

491 ms

forum.js

forum.js

1144 ms

logging.js

logging.js

725 ms

loader.js

loader.js

10486 ms

mo_weibo_follow.js

mo_weibo_follow.js

512 ms

ping.js

ping.js

448 ms

discuz_tips.js

discuz_tips.js

447 ms

background.png

background.png

360 ms

logo.png

logo.png

331 ms

qq_login.gif

qq_login.gif

296 ms

wechat_login.png

wechat_login.png

278 ms

collapsed_no.gif

collapsed_no.gif

445 ms

forum.gif

forum.gif

510 ms

online_admin.gif

online_admin.gif

534 ms

online_supermod.gif

online_supermod.gif

547 ms

online_moderator.gif

online_moderator.gif

566 ms

online_member.gif

online_member.gif

662 ms

logo_88_31.gif

logo_88_31.gif

732 ms

ad_close.gif

ad_close.gif

763 ms

plugin.php

plugin.php

872 ms

switch_width.png

switch_width.png

800 ms

px.png

px.png

799 ms

newarow.gif

newarow.gif

890 ms

pn.png

pn.png

950 ms

nv.png

nv.png

981 ms

qmenu.png

qmenu.png

1009 ms

nv_a.png

nv_a.png

1018 ms

search.png

search.png

1143 ms

pt_item.png

pt_item.png

1181 ms

noavatar_small.gif

noavatar_small.gif

937 ms

shareqq.js

shareqq.js

445 ms

chart.png

chart.png

319 ms

titlebg.png

titlebg.png

319 ms

connect.php

connect.php

473 ms

toss_11.gif

toss_11.gif

226 ms

NTQ5MTg4MTM=.js

NTQ5MTg4MTM=.js

505 ms

scrolltop.png

scrolltop.png

307 ms

widget.html

widget.html

522 ms

widget.css

widget.css

236 ms

widget.js

widget.js

458 ms

shell_v2.js

shell_v2.js

765 ms

qq_share_button.png

qq_share_button.png

284 ms

logger.js

logger.js

375 ms

bds_s_v2.js

bds_s_v2.js

2542 ms

SEO Factors

eeefff.net SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eeefff.net 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 Eeefff.net 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.

Social Sharing Optimization

eeefff.net

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