Oschina.net - SEO Checker - Website Review

Your Website Score is

Similar Ranking

AFRICAN MUSIC ON YOUR PHONE | MDUNDO.COM

mdundo.com

SHOP FOR THE LATEST FASHION & CLOTHING TRENDS AND STYLES | STYLICY USA

stylicy.com

筆記網路

biji.co

LIVEAM.TV — ПОРТАЛ АКТУАЛЬНОГО ВИДЕО

liveam.tv

TELANGANA STATE PORTAL HOME

telangana.gov.in

分享世界的美好【COLATOUR 可樂旅遊】

colatour.com.tw

NEWS.MN - МЭДЭЭЛЛИЙН ЭХ СУРВАЛЖ

news.mn

Latest Sites

AMERICA NO.1 RAMEN MALL

ramenmall.com

SEARCH FOR WHOLESALE PRODUCTS WHOLESALE | SUPPLY LEADER — WHOLESALE SUPPLY

supplyleader.com

home.takepocket.com

ENGINEERING DESTINATION

engineeringdestination.com

BITINCOME.PRO

bitincome.pro

SIMPLY EARN MONEY | MONEY EARNING IDEAS

simplyearnmoney.com

FIEWIN

fiewin.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

35 oschina.net Last Updated: 1 year

Success 70% of passed verification steps

Warning 7% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 74%

Best Practices Desktop Score 69%

SEO Desktop Score 90%

Progressive Web App Desktop Score 54%

Performance Mobile Score 50%

Best Practices Mobile Score 62%

SEO Mobile Score 92%

Progressive Web App Mobile Score 56%

Page Authority Authority 55%

Domain Authority Domain Authority 49%

Moz Rank 5.5/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 20 Characters

OSCHINA - 中文开源技术交流社区

Meta Description 73 Characters

OSCHINA.NET 是目前领先的中文开源技术社区。我们传播开源的理念，推广开源项目，为 IT 开发者提供了一个发现、使用、并交流开源技术的平台

Effective URL 23 Characters

https://www.oschina.net

Excerpt Page content

OSCHINA - 中文开源技术交流社区 ...

Meta Keywords 13 Detected

开源 OSC 开源软件开源硬件开源网站开源社区 java开源 perl开源 python开源 ruby开源 php开源开源项目开源代码

Keywords Cloud Density

java13 oschina7 spring6 每日一博5 cloud4 android4 linux4 码云推荐4 seata3 ￥1003

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
java	13
oschina	7
spring	6
每日一博	5
cloud	4
android	4
linux	4
码云推荐	4
seata	3
￥100	3

Google Preview Your look like this in google search result

OSCHINA - 中文开源技术交流社区

https://www.oschina.net

OSCHINA.NET 是目前领先的中文开源技术社区。我们传播开源的理念，推广开源项目，为 IT 开发者提供了一个发现、使用、并交流开源技术的平台

Robots.txt File Detected

http://oschina.net/robots.txt

Sitemap.xml File No Found

http://oschina.net/sitemap.xml

Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system

Updated: 2018-01-16 / 3 years

Create on: 2008-08-16 / 13 years

Expires on: 2021-08-16 / 1 months 27 days

GoDaddy.com, LLC ,

Registrar Whois Server: whois.godaddy.com

Registrar URL: http://www.godaddy.com

Nameservers

NS1.DNSV2.COM

NS2.DNSV2.COM

Page Size Code & Text Ratio

Document Size: ~181.98 KB

Code Size: ~181.49 KB

Text Size: ~497 B Ratio: 0.27%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Max Potential First Input Delay 170 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 1.8 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Estimated Input Latency 10 ms

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

Remove unused CSS Potential savings of 196 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 1,644 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Reduce server response times (TTFB) Root document took 2,800 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 280 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 220 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 30 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 70 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 0.4 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Defer offscreen images Potential savings of 398 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Properly size images Potential savings of 723 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 4.0 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 1.5 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoid enormous network payloads Total size was 3,107 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 1.6 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 0.7 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 6 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 10 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load

Avoid an excessive DOM size 1,378 elements

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

Minify JavaScript Potential savings of 5 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 0.7 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 88 requests • 3,109 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 65 resources found

A long cache lifetime can speed up repeat visits to your page

Mobile

Reduce server response times (TTFB) Root document took 660 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 1,840 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 220 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 230 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 760 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 1.7 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Defer offscreen images Potential savings of 857 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Properly size images Potential savings of 211 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 5.6 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 7.8 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoid enormous network payloads Total size was 3,100 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 4.8 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 3.1 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 6 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 10 chains found

Avoid an excessive DOM size 1,405 elements

Minify JavaScript Potential savings of 5 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 3.1 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 90 requests • 3,100 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 67 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 700 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 9.0 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

First Contentful Paint (3G) 6660 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Estimated Input Latency 170 ms

Tap targets are sized appropriately 100% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Document uses legible font sizes 99.95% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Remove unused CSS Potential savings of 198 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 1,535 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 
Date: Fri, 27 Dec 2019 01:01:04 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Server: Tengine
Vary: Accept-Encoding
Pragma: must-revalidate, no-cache, private
Cache-Control: no-cache
Expires: Sun, 1 Jan 2000 01:00:00 GMT
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	3074413c.dayugslb.com	212.64.62.174	IN	0
CNAME	oschina.net	3074413c.dayugslb.com	IN	9

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

35 oschina.net Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

jQuery

Semantic-ui

Tengine

Vue js

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments