Tools & Wizards About Us
oeeee.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

oeeee.com

奥一网 - 南都新闻眼，城市生活圈 - oeeee.com

Page Load Speed

33.2 sec in total

First Response

1.6 sec

Resources Loaded

31 sec

Page Rendered

587 ms

oeeee.com screenshot

About Website

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

奥一新闻是广东南都全媒体网络科技有限公司旗下核心新闻平 台，具备互联网新闻信息采编发布服务资质。奥一新闻目前已经搭建立体矩阵传播体系，包括小程序、移动端、网站、奥一官微、奥一财经微信，并通过南都app全网分发内容。

Visit oeeee.com

Key Findings

We analyzed Oeeee.com page load time and found that the first response time was 1.6 sec and then it took 31.6 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

oeeee.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value390 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

oeeee.com

1562 ms

www.oeeee.com

3603 ms

base201512241515.css

6757 ms

index201511031055.css

6312 ms

sea.js

6465 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 6% of them (6 requests) were addressed to the original Oeeee.com, 41% (39 requests) were made to Oeimg2.cache.oeeee.com and 22% (21 requests) were made to Oeeee.adsame.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Oeimg2.cache.oeeee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 411.9 kB (33%)

Content Size

1.3 MB

After Optimization

838.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 62.0 kB

  • Original 83.2 kB
  • After minification 78.3 kB
  • After compression 21.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 62.0 kB or 74% of the original size.

Image Optimization

-12%

Potential reduce by 100.5 kB

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

JavaScript Optimization

-67%

Potential reduce by 172.3 kB

  • Original 258.3 kB
  • After minification 250.0 kB
  • After compression 86.0 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 172.3 kB or 67% of the original size.

CSS Optimization

-80%

Potential reduce by 77.1 kB

  • Original 96.3 kB
  • After minification 88.8 kB
  • After compression 19.1 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. Oeeee.com needs all CSS files to be minified and compressed as it can save up to 77.1 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

91

After Optimization

79

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oeeee.com

oeeee.com

1562 ms

www.oeeee.com

www.oeeee.com

3603 ms

base201512241515.css

base201512241515.css

6757 ms

index201511031055.css

index201511031055.css

6312 ms

sea.js

sea.js

6465 ms

pop_login.css

pop_login.css

6474 ms

s

s

1242 ms

s

s

1266 ms

s

s

1294 ms

s

s

1448 ms

s

s

3234 ms

s

s

1469 ms

s

s

1924 ms

s

s

1983 ms

AD2v1.1.js

AD2v1.1.js

4942 ms

s

s

1953 ms

s

s

2133 ms

s

s

2161 ms

s

s

2642 ms

s

s

2709 ms

s

s

2713 ms

s

s

2883 ms

s

s

1925 ms

s

s

2345 ms

s

s

2448 ms

api.php

api.php

969 ms

s

s

2651 ms

s

s

2786 ms

s

s

2971 ms

index.php

index.php

550 ms

5706ee23d2abd.jpg

5706ee23d2abd.jpg

6168 ms

dcla010801_i_46c5c1e979.jpg

dcla010801_i_46c5c1e979.jpg

11348 ms

57008c3b69f4b.jpg

57008c3b69f4b.jpg

7072 ms

5705b3a6f13c4.jpg

5705b3a6f13c4.jpg

5751 ms

56f9fc854a22d.jpg

56f9fc854a22d.jpg

6647 ms

5707040ccbbd8.jpg

5707040ccbbd8.jpg

12677 ms

56fdd46f8da69.jpg

56fdd46f8da69.jpg

9250 ms

56f3989310543.jpg

56f3989310543.jpg

6186 ms

56ec12e3a2c19.jpg

56ec12e3a2c19.jpg

15423 ms

57074cbfa6bd1.jpg

57074cbfa6bd1.jpg

7128 ms

56ebc60d804f7.jpg

56ebc60d804f7.jpg

10115 ms

logo_1x.png

logo_1x.png

920 ms

icon_oeeee.png

icon_oeeee.png

454 ms

570703b53e1b0.jpg

570703b53e1b0.jpg

3176 ms

57070cb986117.jpg

57070cb986117.jpg

1608 ms

5705b661239be.png

5705b661239be.png

3913 ms

5705b658df027.png

5705b658df027.png

4133 ms

570779c7d7d2d.jpg

570779c7d7d2d.jpg

2107 ms

56f4e56e91a43.jpg

56f4e56e91a43.jpg

2248 ms

56f25d235d364.jpg

56f25d235d364.jpg

6647 ms

56f0bf97c5732.jpg

56f0bf97c5732.jpg

20092 ms

56ec152f97541.jpg

56ec152f97541.jpg

9203 ms

5706fa47e2d13.png

5706fa47e2d13.png

15847 ms

56ea13c5c53f3.jpg

56ea13c5c53f3.jpg

7393 ms

wx_ewm2.jpg

wx_ewm2.jpg

5559 ms

bot-log1.png

bot-log1.png

6027 ms

bot-log2.png

bot-log2.png

7687 ms

bot-log3.png

bot-log3.png

7184 ms

bot-log5.png

bot-log5.png

7750 ms

bot-log6.png

bot-log6.png

8266 ms

bot-log7.png

bot-log7.png

8656 ms

bg_baoliao.png

bg_baoliao.png

10426 ms

number_icon.png

number_icon.png

8676 ms

icon_dot.png

icon_dot.png

9740 ms

ico_cp_2.png

ico_cp_2.png

10706 ms

Vc7oyFc41427438631.jpg

Vc7oyFc41427438631.jpg

11614 ms

NEsTIXEL1427438641.jpg

NEsTIXEL1427438641.jpg

8992 ms

home_loading.gif

home_loading.gif

9418 ms

aKNnc5v91427787359.jpg

aKNnc5v91427787359.jpg

9135 ms

box_new_icon.png

box_new_icon.png

9842 ms

lt_ewm.jpg

lt_ewm.jpg

10457 ms

btn_write.png

btn_write.png

10286 ms

aTj3bbXF1444979795.jpg

aTj3bbXF1444979795.jpg

11799 ms

link_netchina3.png

link_netchina3.png

10985 ms

main.js

main.js

10903 ms

atrk.js

atrk.js

53 ms

analytics.js

analytics.js

34 ms

hm.js

hm.js

925 ms

collect

collect

15 ms

atrk.gif

atrk.gif

41 ms

collect

collect

73 ms

test.png

test.png

255 ms

hm.gif

hm.gif

461 ms

jquery.js

jquery.js

2910 ms

channel.php

channel.php

1584 ms

index.php

index.php

893 ms

grey.gif

grey.gif

523 ms

sso.php

sso.php

544 ms

channel.php

channel.php

4325 ms

channel.php

channel.php

2206 ms

wx_ewm.png

wx_ewm.png

445 ms

home_to_top.png

home_to_top.png

451 ms

yjfk.png

yjfk.png

534 ms

dcza020402_i_4479dfc1c4.jpg

dcza020402_i_4479dfc1c4.jpg

2646 ms

55c0ac3987352.jpg

55c0ac3987352.jpg

2912 ms

dcza060401_i_4479dfc1c4.jpg

dcza060401_i_4479dfc1c4.jpg

2168 ms

Accessibility Review

oeeee.com accessibility score

69

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

oeeee.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

oeeee.com SEO score

91

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

oeeee.com

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