Tools & Wizards About Us
oofof.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

oofof.com

民生广告网 www.oofof.com-免费广告发布,免费信息网

Page Load Speed

54.6 sec in total

First Response

3.2 sec

Resources Loaded

50.2 sec

Page Rendered

1.2 sec

oofof.com screenshot

About Website

Click here to check amazing Oofof content for China. Otherwise, check out these important facts you probably never knew about oofof.com

民生广告网是一个免费的民生信息广告平台，关注民生，服务民生，低碳生活从民生广告开始。

Visit oofof.com

Key Findings

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

Performance Metrics

oofof.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value3,780 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

oofof.com

3194 ms

sty.css

13332 ms

AC_RunActiveContent.js

18661 ms

gb2big50.js

8847 ms

inlay.js

1862 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 47% of them (46 requests) were addressed to the original Oofof.com, 9% (9 requests) were made to Dspcm.brand.sogou.com and 6% (6 requests) were made to Inte.sogou.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Oofof.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 227.9 kB (43%)

Content Size

524.2 kB

After Optimization

296.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Oofof.com main page is 524.2 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. 20% of websites need less resources to load. Images take 232.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 63.2 kB

  • Original 81.5 kB
  • After minification 73.9 kB
  • After compression 18.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. 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 63.2 kB or 78% of the original size.

Image Optimization

-17%

Potential reduce by 40.4 kB

  • Original 232.0 kB
  • After minification 191.6 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, Oofof needs image optimization as it can save up to 40.4 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 124.2 kB

  • Original 210.7 kB
  • After minification 207.3 kB
  • After compression 86.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 124.2 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (21%)

Requests Now

62

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oofof.com

oofof.com

3194 ms

sty.css

sty.css

13332 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

18661 ms

gb2big50.js

gb2big50.js

8847 ms

inlay.js

inlay.js

1862 ms

c.js

c.js

3519 ms

min.js

min.js

20363 ms

stat.php

stat.php

2825 ms

f.js

f.js

1326 ms

d.jpg

d.jpg

11235 ms

Connect_logo_3.png

Connect_logo_3.png

1096 ms

n1.gif

n1.gif

7102 ms

logo_m.gif

logo_m.gif

949 ms

free.gif

free.gif

1101 ms

ao5.gif

ao5.gif

2848 ms

ao4.gif

ao4.gif

3830 ms

tar_big.gif

tar_big.gif

8085 ms

1363567533.gif

1363567533.gif

3322 ms

ao2.gif

ao2.gif

9245 ms

1376656039.jpg

1376656039.jpg

19788 ms

1378179803.jpg

1378179803.jpg

19789 ms

1429801672.jpg

1429801672.jpg

19790 ms

1410838056.jpg

1410838056.jpg

19482 ms

1363568061.jpg

1363568061.jpg

19791 ms

1417162879.jpg

1417162879.jpg

19792 ms

1366860843.jpg

1366860843.jpg

19796 ms

1439824931.jpg

1439824931.jpg

19797 ms

1430211199.jpg

1430211199.jpg

19797 ms

1426229630.jpg

1426229630.jpg

19797 ms

1459673430.gif

1459673430.gif

19798 ms

1409284792.jpg

1409284792.jpg

19799 ms

animated_favicon1.gif

animated_favicon1.gif

19800 ms

wangan.gif

wangan.gif

19800 ms

cyberhome.gif

cyberhome.gif

19800 ms

home_b.gif

home_b.gif

19801 ms

oofof.jpg

oofof.jpg

19800 ms

biaoshi.gif

biaoshi.gif

19800 ms

sou.gif

sou.gif

19781 ms

fabgt.gif

fabgt.gif

19780 ms

logoi.gif

logoi.gif

19780 ms

d2.gif

d2.gif

19781 ms

bai6.gif

bai6.gif

19780 ms

d22.gif

d22.gif

19780 ms

bg.jpg

bg.jpg

19781 ms

throw

throw

2353 ms

ask

ask

4613 ms

ask_service

ask_service

1236 ms

o1.gif

o1.gif

19843 ms

m.gif

m.gif

19697 ms

y_bg.gif

y_bg.gif

19692 ms

monitor.js

monitor.js

36 ms

m.js

m.js

39 ms

runtime.js

runtime.js

29 ms

link.js

link.js

11 ms

cm.mediav.com

cm.mediav.com

1436 ms

logo2.png

logo2.png

53 ms

m3.gif

m3.gif

18168 ms

aox.jpg

aox.jpg

19958 ms

cm

cm

927 ms

ct

ct

1823 ms

lm.jpg

lm.jpg

1912 ms

pe.js

pe.js

453 ms

ask

ask

1951 ms

qi

qi

1483 ms

log_print

log_print

874 ms

bf3c7f0c-4c88-4658-a842-4dd5d07f9f0b.jpg

bf3c7f0c-4c88-4658-a842-4dd5d07f9f0b.jpg

10929 ms

sogou_icon_wz_1.png

sogou_icon_wz_1.png

2098 ms

fc.js

fc.js

229 ms

ct

ct

13489 ms

lm.jpg

lm.jpg

453 ms

ask

ask

363 ms

t.gif

t.gif

3784 ms

t.gif

t.gif

836 ms

ct

ct

1468 ms

top.jpg

top.jpg

14918 ms

stat.htm

stat.htm

164 ms

core.php

core.php

981 ms

qi

qi

442 ms

pixel

pixel

769 ms

qqcm

qqcm

1477 ms

9.gif

9.gif

2063 ms

pic.gif

pic.gif

763 ms

close.jpg

close.jpg

352 ms

throw

throw

3936 ms

throw

throw

4096 ms

8470edf6-c06c-4e87-bb24-783904da942e.gif

8470edf6-c06c-4e87-bb24-783904da942e.gif

3030 ms

qi

qi

4368 ms

app.gif

app.gif

1075 ms

pixel

pixel

2841 ms

imagelink.js

imagelink.js

15 ms

t012122965682c9c008.jpg

t012122965682c9c008.jpg

8440 ms

t019536a4449c46d9d5.jpg

t019536a4449c46d9d5.jpg

17627 ms

t011913fb04b7264d1f.jpg

t011913fb04b7264d1f.jpg

341 ms

t.gif

t.gif

756 ms

t.gif

t.gif

1533 ms

qqcm

qqcm

5701 ms

pixel

pixel

443 ms

pixel

pixel

439 ms

Accessibility Review

oofof.com accessibility score

61

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

oofof.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

oofof.com SEO score

62

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Oofof.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 Oofof.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.

Social Sharing Optimization

oofof.com

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