Your Website Score is

Similar Ranking

87
.NET |---. CROSS-PLATFORM. OPEN SOURCE.
windows.net
87
CCM - ONLINE COMMUNITY
ccm.net
87
GOOGLE
google.fi
87
東洋経済オンライン | 経済ニュースの新基準
toyokeizai.net
87
店铺浏览-淘宝网
janeeyre.tmall.com
87
COMO CRIAR UM SITE GRÁTIS | DESCUBRA COMO CRIAR UM SITE GRÁTIS - WEBNODE
webnode.com.br
87
WELCOME TO PYTHON.ORG
python.org

Latest Sites

14
FINYA LIMITED
finyalimited.com
14
CADOCINVESTMENT.COM | AUSTRALIAN INVESTMENT COMPANY
cadocinvestment.com
14
NGF LEGAL – CORPORATE LAWYER AGENCY
ngflegal.com
14
GLOBAL LOGISTICS AUSTRALIA | GLOBAL LOGISTICS LIMITED
globallogisticslimited.com
50
THE GUY R COOK REPORT BLOG
guyrcook.com
26
CLOKIDS
clokids.shop

Top Technologies

Nginx
Web Servers
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

87 oricon.co.jp Last Updated: 12 months

Success 62% of passed verification steps
Warning 15% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 59%
Best Practices Desktop Score 62%
SEO Desktop Score 100%
Progressive Web App Desktop Score 27%
Performance Mobile Score 25%
Best Practices Mobile Score 54%
SEO Mobile Score 92%
Progressive Web App Mobile Score 33%
Page Authority Authority 54%
Domain Authority Domain Authority 89%
Moz Rank 5.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: SHIFT_JIS
Title Tag 31 Characters
ORICON NEWS|最新情報を発信する総合トレンドメディア
Meta Description 75 Characters
芸能・音楽・ランキングなどオリコンならではのエンタメ情報はもちろん、信頼できる媒体の信頼できる情報を幅広いジャンルにわたり提供する総合トレンドメディア
Effective URL 24 Characters
https://www.oricon.co.jp
Excerpt Page content
ORICON NEWS|最新情報を発信する総合トレンドメディア ORICON NEWS|オリコンニュースニュース・特集芸能人名画像CDDVD&Blu-ray歌詞 FacebookTwitterInstagramYoutubeトップ芸能音楽ドラマ&映画アニ...
Keywords Cloud Density
|ライフ|25 ランキング7 |マンガ|6 採用担当向け5 |おでかけ|5 その名も5 通信講座5 ニューストップ5 新築分譲マンション4 |アニメ|4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
|ライフ| 25
ランキング 7
|マンガ| 6
採用担当向け 5
|おでかけ| 5
その名も 5
通信講座 5
ニューストップ 5
新築分譲マンション 4
|アニメ| 4
Google Preview Your look like this in google search result
ORICON NEWS|最新情報を発信する総合トレンドメディア
https://www.oricon.co.jp
芸能・音楽・ランキングなどオリコンならではのエンタメ情報はもちろん、信頼できる媒体の信頼できる情報を幅広いジャンルにわたり提供する総合トレンドメディア
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~381.55 KB
Code Size: ~358.13 KB
Text Size: ~23.42 KB Ratio: 6.14%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

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

Desktop

Desktop Screenshot
Serve static assets with an efficient cache policy 116 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 180 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 4.4 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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 18.7 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 40 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
Minify CSS Potential savings of 20 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 92 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 120 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 1,140 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 80 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 37 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 9 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code Third-party code blocked the main thread for 260 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 170 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 2.1 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 253 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 87 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 3.1 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.6 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).
Avoids enormous network payloads Total size was 2,043 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 4.3 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 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 21 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 3,489 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 32 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 270 requests • 2,043 KB
To set budgets for the quantity and size of page resources, add a budget.json file

Mobile

Mobile Screenshot
Minify CSS Potential savings of 11 KB
Minifying CSS files can reduce network payload sizes
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 91.18% 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 71 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 74 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 970 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 300 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 4 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code Third-party code blocked the main thread for 2,400 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 2,930 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 9.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Defer offscreen images Potential savings of 154 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 40 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 13.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 13.6 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,174 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 20.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 2.5 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 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 19 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 3,317 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 6 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 2.6 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 221 requests • 3,174 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 131 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 430 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 20.2 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
Page load is not fast enough on mobile networks Interactive at 20.2 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 190 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
First Contentful Paint (3G) 4946 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

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 OK
Date: Wed, 27 Nov 2019 09:12:10 GMT
Server: Apache
Content-Type: text/html; charset=Shift_JIS
Set-Cookie: Apache=35.226.1.23.1574845930159630; path=/; domain=.oricon.co.jp
Vary: Accept-Encoding,env=!dont-vary
Content-Encoding: gzip
Content-Length: 20
Connection: close
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome