Access oome.org. 上海曲德曲网络科技有限公司

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

www.oome.org

1709 ms

prettyPhoto.css

490 ms

pagenavi-css.css

493 ms

reset.css

493 ms

text.css

498 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 91% of them (75 requests) were addressed to the original Oome.org, 4% (3 requests) were made to Static.duoshuo.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Oome.org.

Content Size

686.8 kB

After Optimization

335.2 kB

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

HTML Optimization

-81%

Potential reduce by 29.4 kB

Original 36.3 kB
After minification 31.9 kB
After compression 6.9 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 4.4 kB, which is 12% 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 29.4 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 24.7 kB

Original 239.0 kB
After minification 214.3 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. Oome images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 151.5 kB

Original 238.9 kB
After minification 196.0 kB
After compression 87.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 151.5 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 146.1 kB

Original 172.7 kB
After minification 144.1 kB
After compression 26.6 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. Oome.org needs all CSS files to be minified and compressed as it can save up to 146.1 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Definition list items are not wrapped in <dl> elements

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

High

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

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

N/A
Language Claimed

ZH
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oome.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Chinese. Our system also found out that Oome.org 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

oome.org

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

Report Summary

Performance

Accessibility

Best Practices

SEO

上海曲德曲网络科技有限公司

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

www.oome.org

prettyPhoto.css

pagenavi-css.css

reset.css

text.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

www.oome.org

prettyPhoto.css

pagenavi-css.css

reset.css

text.css

960.css

superfish.css

style.css

custom_style.php

jquery-1.4.2.min.js

jquery.prettyPhoto.js

swfobject.js

superfish.combined.js

script.js

embed.js

shCore.js

shBrushAS3.js

shBrushBash.js

shBrushColdFusion.js

shBrushClojure.js

shBrushCpp.js

shBrushCSharp.js

shBrushCss.js

shBrushDelphi.js

shBrushDiff.js

shBrushErlang.js

shBrushFSharp.js

shBrushGroovy.js

shBrushJava.js

shBrushJavaFX.js

shBrushJScript.js

shBrushLatex.js

shBrushMatlabKey.js

shBrushObjC.js

shBrushPerl.js

shBrushPhp.js

shBrushPlain.js

shBrushPowerShell.js

shBrushPython.js

shBrushR.js

shBrushRuby.js

shBrushScala.js

shBrushSql.js