Matome-Plus.Net - Info matome-plus.net

matome-plus.net receives about 57,689 unique visitors and 259,598 (4.50 per visitor) page views per day which should earn about $830.71/day from advertising revenue. Estimated site value is $457,767.58. According to Alexa Traffic Rank matome-plus.net is ranked number 18,607 in the world and 0.0034% of global Internet users visit it. Site is hosted in Osaka, Ōsaka, 543-0062, Japan and links to network IP address 49.212.66.204. This server doesn't support HTTPS and doesn't support HTTP/2.

About - matome-plus.net

「人気のまとめサイト」をまとめています
Edit Site Info

Technologies used on Website

Currently Not Available

matome-plus.net Profile

Title: まとめサイト速報+
Keywords: まとめ,まとめサイト,まとめサイト速報,matome,2ch
Last update was 240 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with matome-plus.net in any way. Only publicly available statistics data are displayed.

How popular is matome-plus.net?

57.7K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
57,689
Monthly Unique Visitors:
1,384,536
Pages per Visit:
4.50
Daily Pageviews:
259,598
Alexa Rank:
18,607 visit alexa
Alexa Reach:
0.0034%   (of global internet users)
Avg. visit duration:
16:43
Bounce rate:
24.06%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
25.04%
Referral:
64.71%
Search:
9.95%
Social:
0.29%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
Japan 99.8%100.0%1632

Where do visitors go on this site?

Reach%Pageviews%PerUser
matome-plus.net
100.00%100.00%4.5

Competitive Data

SEMrush
Domain:
  matome-plus.net
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is matome-plus.net?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
matome-plus.net
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
matome-plus.net
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much matome-plus.net can earn?

Daily Revenue:
$830.71
Monthly Revenue:
$24,921.30
Yearly Revenue:
$303,209.15
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Japan 259,598$830.71

How much money do matome-plus.net lose due to Adblock?

Daily Revenue Loss:
$24.92
Monthly Revenue Loss:
$747.64
Yearly Revenue Loss:
$9,096.31
Daily Pageviews Blocked:
7,788
Monthly Pageviews Blocked:
233,638
Yearly Pageviews Blocked:
2,842,598
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Japan 7,788$24.92

How much is matome-plus.net worth?

Website Value:
$457,767.58

+ Where is matome-plus.net hosted?

Server IP:
49.212.66.204
ASN:
AS7684 
ISP:
SAKURA Internet Inc. 
Server Location:
Osaka
Ōsaka, 27
543-0062
Japan, JP
 

Other sites hosted on 49.212.66.204

There are no other sites hosted on this IP

+ How fast does matome-plus.net load?

Average Load Time:
(184 ms) 99 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)818ms 92% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 92% 5% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 5% 1% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 1%
First Input Delay (FID)5ms 99% of loads for this page have a fast (<50ms) First Input Delay (FID) 99% 0% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an FAST speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)527ms 96% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 96% 2% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 2% 0% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 0%
First Input Delay (FID)4ms 99% of loads for this page have a fast (<50ms) First Input Delay (FID) 99% 0% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Lab Data

Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
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. Learn more.
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. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Enable text compression - Potential savings of 29 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://matome-plus.net/style.css
25 KB21 KB
http://matome-plus.net/
12 KB9 KB
Efficiently encode images - Potential savings of 24 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://matome-plus.net/images/raiza.jpg
14 KB7 KB
http://matome-plus.net/images/skytube24.jpg
14 KB7 KB
http://matome-plus.net/images/kotori20.jpg
9 KB5 KB
http://matome-plus.net/images/san.jpg
13 KB5 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://matome-plus.net/
0 ms284 ms13 KB12 KB200text/htmlDocument
http://matome-plus.net/style.css
297 ms673 ms25 KB25 KB200text/cssStylesheet
http://matome-plus.net/images/dqnplus-logo.jpg
297 ms674 ms10 KB10 KB200image/jpegImage
http://matome-plus.net/images/rss-icon1.gif
298 ms794 ms1 KB1 KB200image/gifImage
http://matome-plus.net/images/alfa-logo.jpg
299 ms484 ms11 KB11 KB200image/jpegImage
http://matome-plus.net/images/news4vip-logo.jpg
300 ms714 ms12 KB11 KB200image/jpegImage
http://matome-plus.net/images/hamusoku-logo10.jpg
300 ms683 ms11 KB11 KB200image/jpegImage
http://matome-plus.net/images/himasoku-logo13.jpg
300 ms858 ms11 KB11 KB200image/jpegImage
http://matome-plus.net/images/vippernaore-logo5.jpg
300 ms1042 ms11 KB11 KB200image/jpegImage
http://matome-plus.net/images/skytube24.jpg
300 ms866 ms14 KB14 KB200image/jpegImage
http://matome-plus.net/images/raiza.jpg
300 ms1078 ms14 KB14 KB200image/jpegImage
http://matome-plus.net/images/san.jpg
301 ms1139 ms13 KB13 KB200image/jpegImage
http://matome-plus.net/images/kotori20.jpg
301 ms1131 ms10 KB9 KB200image/jpegImage
http://matome-plus.net/images/header-bg.gif
678 ms1149 ms0 KB0 KB200image/gifImage
http://matome-plus.net/images/navi-bg.jpg
679 ms1244 ms1 KB0 KB200image/jpegImage
http://matome-plus.net/images/navi-pink.gif
679 ms1423 ms1 KB1 KB200image/gifImage
http://matome-plus.net/style.css
679 ms1283 ms25 KB25 KB200text/cssImage
http://matome-plus.net/images/title-bg01.gif
680 ms1657 ms5 KB4 KB200image/gifImage
http://matome-plus.net/images/div-y.gif
681 ms1350 ms0 KB0 KB200image/gifImage
http://matome-plus.net/images/div-x.gif
681 ms1349 ms0 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 19 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://matome-plus.net/style.css
604800000 ms25 KB
http://matome-plus.net/style.css
604800000 ms25 KB
http://matome-plus.net/images/raiza.jpg
2419200000 ms14 KB
http://matome-plus.net/images/skytube24.jpg
2419200000 ms14 KB
http://matome-plus.net/images/san.jpg
2419200000 ms13 KB
http://matome-plus.net/images/news4vip-logo.jpg
2419200000 ms12 KB
http://matome-plus.net/images/alfa-logo.jpg
2419200000 ms11 KB
http://matome-plus.net/images/hamusoku-logo10.jpg
2419200000 ms11 KB
http://matome-plus.net/images/himasoku-logo13.jpg
2419200000 ms11 KB
http://matome-plus.net/images/vippernaore-logo5.jpg
2419200000 ms11 KB
http://matome-plus.net/images/dqnplus-logo.jpg
2419200000 ms10 KB
http://matome-plus.net/images/kotori20.jpg
2419200000 ms10 KB
http://matome-plus.net/images/title-bg01.gif
2419200000 ms5 KB
http://matome-plus.net/images/navi-pink.gif
2419200000 ms1 KB
http://matome-plus.net/images/rss-icon1.gif
2419200000 ms1 KB
http://matome-plus.net/images/navi-bg.jpg
2419200000 ms1 KB
http://matome-plus.net/images/header-bg.gif
2419200000 ms0 KB
http://matome-plus.net/images/div-x.gif
2419200000 ms0 KB
http://matome-plus.net/images/div-y.gif
2419200000 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
310 ms
7 ms
319 ms
6 ms
325 ms
6 ms
699 ms
158 ms
865 ms
29 ms
900 ms
9 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
258 ms3 ms1 ms
Minify CSS - Potential savings of 5 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
http://matome-plus.net/style.css
25 KB5 KB
Remove unused CSS - Potential savings of 17 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. Learn more.

URL
SizePotential Savings
http://matome-plus.net/style.css
25 KB17 KB
Avoids enormous network payloads - Total size was 189 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://matome-plus.net/style.css
25 KB
http://matome-plus.net/style.css
25 KB
http://matome-plus.net/images/raiza.jpg
14 KB
http://matome-plus.net/images/skytube24.jpg
14 KB
http://matome-plus.net/images/san.jpg
13 KB
http://matome-plus.net/
13 KB
http://matome-plus.net/images/news4vip-logo.jpg
12 KB
http://matome-plus.net/images/alfa-logo.jpg
11 KB
http://matome-plus.net/images/hamusoku-logo10.jpg
11 KB
http://matome-plus.net/images/himasoku-logo13.jpg
11 KB
Minimizes main-thread work - 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
162 ms
Rendering
49 ms
Other
38 ms
Parse HTML & CSS
6 ms
Script Evaluation
3 ms
Script Parsing & Compilation
1 ms
Serve images in next-gen formats - Potential savings of 28 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. Learn more.

URL
SizePotential Savings
http://matome-plus.net/images/raiza.jpg
14 KB10 KB
http://matome-plus.net/images/skytube24.jpg
14 KB10 KB
http://matome-plus.net/images/san.jpg
13 KB8 KB
Avoids an excessive DOM size - 234 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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). Learn more.

Statistic
ElementValue
Total DOM Elements
234
Maximum DOM Depth
9
Maximum Child Elements
19
Keep request counts low and transfer sizes small - 20 requests • 189 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
20189 KB
Image
18151 KB
Stylesheet
125 KB
Document
113 KB
Media
00 KB
Font
00 KB
Script
00 KB
Other
00 KB
Third-party
00 KB
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 290 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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

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. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

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. Learn more.

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

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Minimize Critical Requests Depth - 1 chain 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. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)1.3s 92% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 81% 16% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 16% 2% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 2%
First Input Delay (FID)273ms 1% of loads for this page have a fast (<50ms) First Input Delay (FID) 1% 82% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 82% 16% of loads for this page have a slow (>250ms) First Input Delay (FID) 16%

Origin Data

All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)1.0s 89% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 89% 9% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 9% 1% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 1%
First Input Delay (FID)267ms 99% of loads for this page have a fast (<50ms) First Input Delay (FID) 1% 86% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 86% 12% of loads for this page have a slow (>250ms) First Input Delay (FID) 12%

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
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. Learn more.
First Contentful Paint (3G) 1860 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
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. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Serve images in next-gen formats - Potential savings of 28 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. Learn more.

URL
SizePotential Savings
http://matome-plus.net/images/raiza.jpg
14 KB10 KB
http://matome-plus.net/images/skytube24.jpg
14 KB10 KB
http://matome-plus.net/images/san.jpg
13 KB8 KB
Avoids an excessive DOM size - 234 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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). Learn more.

Statistic
ElementValue
Total DOM Elements
234
Maximum DOM Depth
9
Maximum Child Elements
19
Keep request counts low and transfer sizes small - 20 requests • 189 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
20189 KB
Image
18151 KB
Stylesheet
125 KB
Document
113 KB
Media
00 KB
Font
00 KB
Script
00 KB
Other
00 KB
Third-party
00 KB
Efficiently encode images - Potential savings of 24 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://matome-plus.net/images/raiza.jpg
14 KB7 KB
http://matome-plus.net/images/skytube24.jpg
14 KB7 KB
http://matome-plus.net/images/kotori20.jpg
9 KB5 KB
http://matome-plus.net/images/san.jpg
13 KB5 KB
Enable text compression - Potential savings of 29 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://matome-plus.net/style.css
25 KB21 KB
http://matome-plus.net/
12 KB9 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://matome-plus.net/
0 ms375 ms13 KB12 KB200text/htmlDocument
http://matome-plus.net/style.css
389 ms589 ms25 KB25 KB200text/cssStylesheet
http://matome-plus.net/images/dqnplus-logo.jpg
390 ms610 ms10 KB10 KB200image/jpegImage
http://matome-plus.net/images/rss-icon1.gif
390 ms781 ms1 KB1 KB200image/gifImage
http://matome-plus.net/images/alfa-logo.jpg
392 ms599 ms11 KB11 KB200image/jpegImage
http://matome-plus.net/images/news4vip-logo.jpg
392 ms780 ms12 KB11 KB200image/jpegImage
http://matome-plus.net/images/hamusoku-logo10.jpg
392 ms782 ms11 KB11 KB200image/jpegImage
http://matome-plus.net/images/himasoku-logo13.jpg
392 ms791 ms11 KB11 KB200image/jpegImage
http://matome-plus.net/images/vippernaore-logo5.jpg
393 ms810 ms11 KB11 KB200image/jpegImage
http://matome-plus.net/images/skytube24.jpg
393 ms866 ms14 KB14 KB200image/jpegImage
http://matome-plus.net/images/raiza.jpg
393 ms987 ms14 KB14 KB200image/jpegImage
http://matome-plus.net/images/san.jpg
393 ms969 ms13 KB13 KB200image/jpegImage
http://matome-plus.net/images/kotori20.jpg
393 ms986 ms10 KB9 KB200image/jpegImage
http://matome-plus.net/images/header-bg.gif
593 ms988 ms0 KB0 KB200image/gifImage
http://matome-plus.net/images/navi-bg.jpg
594 ms1010 ms1 KB0 KB200image/jpegImage
http://matome-plus.net/images/navi-pink.gif
594 ms1085 ms1 KB1 KB200image/gifImage
http://matome-plus.net/style.css
595 ms1203 ms25 KB25 KB200text/cssImage
http://matome-plus.net/images/title-bg01.gif
596 ms1162 ms5 KB4 KB200image/gifImage
http://matome-plus.net/images/div-y.gif
597 ms1223 ms0 KB0 KB200image/gifImage
http://matome-plus.net/images/div-x.gif
598 ms1191 ms0 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 19 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://matome-plus.net/style.css
604800000 ms25 KB
http://matome-plus.net/style.css
604800000 ms25 KB
http://matome-plus.net/images/raiza.jpg
2419200000 ms14 KB
http://matome-plus.net/images/skytube24.jpg
2419200000 ms14 KB
http://matome-plus.net/images/san.jpg
2419200000 ms13 KB
http://matome-plus.net/images/news4vip-logo.jpg
2419200000 ms12 KB
http://matome-plus.net/images/alfa-logo.jpg
2419200000 ms11 KB
http://matome-plus.net/images/hamusoku-logo10.jpg
2419200000 ms11 KB
http://matome-plus.net/images/himasoku-logo13.jpg
2419200000 ms11 KB
http://matome-plus.net/images/vippernaore-logo5.jpg
2419200000 ms11 KB
http://matome-plus.net/images/dqnplus-logo.jpg
2419200000 ms10 KB
http://matome-plus.net/images/kotori20.jpg
2419200000 ms10 KB
http://matome-plus.net/images/title-bg01.gif
2419200000 ms5 KB
http://matome-plus.net/images/navi-pink.gif
2419200000 ms1 KB
http://matome-plus.net/images/rss-icon1.gif
2419200000 ms1 KB
http://matome-plus.net/images/navi-bg.jpg
2419200000 ms1 KB
http://matome-plus.net/images/header-bg.gif
2419200000 ms0 KB
http://matome-plus.net/images/div-x.gif
2419200000 ms0 KB
http://matome-plus.net/images/div-y.gif
2419200000 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
405 ms
9 ms
415 ms
8 ms
423 ms
6 ms
619 ms
208 ms
836 ms
14 ms
852 ms
14 ms
Minify CSS - Potential savings of 5 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
http://matome-plus.net/style.css
25 KB5 KB
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
1215 ms12 ms4 ms
Remove unused CSS - Potential savings of 17 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. Learn more.

URL
SizePotential Savings
http://matome-plus.net/style.css
25 KB17 KB
Avoids enormous network payloads - Total size was 189 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://matome-plus.net/style.css
25 KB
http://matome-plus.net/style.css
25 KB
http://matome-plus.net/images/raiza.jpg
14 KB
http://matome-plus.net/images/skytube24.jpg
14 KB
http://matome-plus.net/images/san.jpg
13 KB
http://matome-plus.net/
13 KB
http://matome-plus.net/images/news4vip-logo.jpg
12 KB
http://matome-plus.net/images/alfa-logo.jpg
11 KB
http://matome-plus.net/images/hamusoku-logo10.jpg
11 KB
http://matome-plus.net/images/himasoku-logo13.jpg
11 KB
Minimizes main-thread work - 1.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
858 ms
Other
161 ms
Rendering
150 ms
Parse HTML & CSS
30 ms
Script Evaluation
12 ms
Script Parsing & Compilation
4 ms
Minimize Critical Requests Depth - 1 chain 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. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 380 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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

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. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

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

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. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

まとめサイト速報+ renders only 5 pixels tall (13 CSS pixels) .
TOP renders only 5 pixels tall (13 CSS pixels) .
おもしろ and 10 others render only 5 pixels tall (13 CSS pixels) .
アルファルファモザイク and 5 others render only 5 pixels tall (12 CSS pixels) .
昔の料理人「…ハァッ!ハァッ…こでパイナップルをひと... and 23 others render only 5 pixels tall (12 CSS pixels) .
1 renders only 6 pixels tall (15 CSS pixels) .
next and 17 others render only 4 pixels tall (10 CSS pixels) .
新着一覧 renders only 3 pixels tall (9 CSS pixels) .
| and 4 others render only 3 pixels tall (9 CSS pixels) .
VIP renders only 3 pixels tall (9 CSS pixels) .
ニュース renders only 3 pixels tall (9 CSS pixels) .
短レス renders only 3 pixels tall (9 CSS pixels) .
やる夫 renders only 3 pixels tall (9 CSS pixels) .
その他 renders only 3 pixels tall (9 CSS pixels) .
ライザのアトリエ ~常闇の女…[ライザリン・シュタウト] and 3 others render only 5 pixels tall (12 CSS pixels) .
copyright © ま…ghts Reserved. renders only 5 pixels tall (12 CSS pixels) .

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://matome-plus.net/">まとめサイト速報+</a> is close to 2 other tap targets .
The tap target <a href="http://matome-plus.net/">TOP</a> is close to 1 other tap targets .
The tap target <a href="2ch-1.html">2ch</a> and 10 others are close to other tap targets .
The tap target <a href="http://blog.li…s/1994181.html">【画像】 ミニマリストの部屋がヤバすぎると話題に</a> and 23 others are close to other tap targets .
The tap target <a href="http://hamusoku.com/">ハムスター速報</a> and 2 others are close to other tap targets .
The tap target <a href="2ch-1.html" class="currentpage">1</a> is close to 4 other tap targets .
The tap target <a href="2ch-2.html">2</a> and 17 others are close to other tap targets .
The tap target <a href="newentrylist.html">新着一覧</a> is close to 6 other tap targets .
The tap target <a href="2ch-2.html">VIP</a> is close to 7 other tap targets .
The tap target <a href="2ch-10.html">ニュース</a> is close to 6 other tap targets .
The tap target <a href="2ch-14.html">短レス</a> is close to 7 other tap targets .
The tap target <a href="2ch-16.html">やる夫</a> is close to 7 other tap targets .
The tap target <a href="2ch-17.html">その他</a> is close to 5 other tap targets .

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

http://matome-plus.net/style.css

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 60KiB (51% reduction).

Compressing http://matome-plus.net/images/raiza.jpg could save 8.8KiB (62% reduction).
Compressing http://matome-plus.net/images/skytube24.jpg could save 8.5KiB (62% reduction).
Compressing http://matome-plus.net/images/san.jpg could save 6.5KiB (50% reduction).
Compressing http://matome-plus.net/images/kotori20.jpg could save 5.9KiB (63% reduction).
Compressing http://matome-plus.net/images/hamusoku-logo10.jpg could save 5.1KiB (47% reduction).
Compressing http://matome-plus.net/images/news4vip-logo.jpg could save 5KiB (45% reduction).
Compressing http://matome-plus.net/images/himasoku-logo13.jpg could save 5KiB (47% reduction).
Compressing http://matome-plus.net/images/alfa-logo.jpg could save 4.7KiB (42% reduction).
Compressing http://matome-plus.net/images/dqnplus-logo.jpg could save 4.5KiB (46% reduction).
Compressing http://matome-plus.net/images/vippernaore-logo5.jpg could save 4.4KiB (43% reduction).
Compressing http://matome-plus.net/images/title-bg10.jpg could save 858B (56% reduction).
Compressing http://matome-plus.net/images/navi-pink.gif could save 831B (70% reduction).

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 29.2KiB (79% reduction).

Compressing http://matome-plus.net/style.css could save 20.6KiB (83% reduction).
Compressing http://matome-plus.net/ could save 8.7KiB (70% reduction).

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 3.5KiB (15% reduction).

Minifying http://matome-plus.net/style.css could save 3.5KiB (15% reduction).
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does matome-plus.net use compression?

matome-plus.net does not use compression.
Original size: 12.31 KB
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  68
Vendor reliability:
  68
Privacy:
  68
Child safety:
  69

+ SSL Checker - SSL Certificate Verify

matome-plus.net does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

matome-plus.net does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Sat, 28 Sep 2019 21:57:17 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
X-Powered-By: PHP/7.3.9

+ DNS Lookup

Type Ip Target TTL
SOA 3600
Mname master.dns.ne.jp
Rname tech.sakura.ad.jp
Serial Number 2012033114
Refresh 3600
Retry 900
Expire 3600000
Minimum TTL 0
MX matome-plus.net 3600
A 49.212.66.204 3600
NS ns2.dns.ne.jp 3599
NS ns1.dns.ne.jp 3599

+ Whois Lookup

Domain Created:
2009-11-18
Domain Age:
9 years 10 months 10 days  
WhoIs:
 

whois lookup at whois.discount-domain.com...
Domain Name: matome-plus.net
Registry Domain ID: 1576120525_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.discount-domain.com
Registrar URL: http://www.onamae.com
Updated Date: 2018-09-19T00:00:00Z
Creation Date: 2009-11-18T00:00:00Z
Registrar Registration Expiration Date: 2019-11-18T00:00:00Z
Registrar: GMO INTERNET, INC.
Registrar IANA ID: 49
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +81.337709199
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Whois Privacy Protection Service by MuuMuuDomain
Registrant Organization: Whois Privacy Protection Service by MuuMuuDomain
Registrant Street: 2-7-21 Tenjin Chuo-ku
Registrant Street: Tenjin Prime 8F
Registrant City: ***uoka-shi
Registrant State/Province: ***uoka
Registrant Postal Code: 810-0001
Registrant Country: JP
Registrant Phone: +81.927137999
Registrant Phone Ext:
Registrant Fax: +81.927137944
Registrant Fax Ext:
Registrant Email: email
Registry Admin ID: Not Available From Registry
Admin Name: Whois Privacy Protection Service by MuuMuuDomain
Admin Organization: Whois Privacy Protection Service by MuuMuuDomain
Admin Street: 2-7-21 Tenjin Chuo-ku
Admin Street: Tenjin Prime 8F
Admin City: ***uoka-shi
Admin State/Province: ***uoka
Admin Postal Code: 810-0001
Admin Country: JP
Admin Phone: +81.927137999
Admin Phone Ext:
Admin Fax: +81.927137944
Admin Fax Ext:
Admin Email: email
Registry Tech ID: Not Available From Registry
Tech Name: Whois Privacy Protection Service by MuuMuuDomain
Tech Organization: Whois Privacy Protection Service by MuuMuuDomain
Tech Street: 2-7-21 Tenjin Chuo-ku
Tech Street: Tenjin Prime 8F
Tech City: ***uoka-shi
Tech State/Province: ***uoka
Tech Postal Code: 810-0001
Tech Country: JP
Tech Phone: +81.927137999
Tech Phone Ext:
Tech Fax: +81.927137944
Tech Fax Ext:
Tech Email: email
Name Server: ns1.dns.ne.jp
Name Server: ns2.dns.ne.jp
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2018-09-19T00:00:00Z <<<

For more information on Whois status codes, please visit https://icann.org/epp
whois lookup at whois.crsnic.net...
Domain Name: MATOME-PLUS.NET
Registry Domain ID: 1576120525_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.discount-domain.com
Registrar URL: http://gmo.jp
Updated Date: 2018-09-19T08:01:20Z
Creation Date: 2009-11-18T08:29:50Z
Registry Expiry Date: 2019-11-18T08:29:50Z
Registrar: GMO Internet, Inc. d/b/a Onamae.com
Registrar IANA ID: 49
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +81.337709199
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.DNS.NE.JP
Name Server: NS2.DNS.NE.JP
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2019-09-28T21:57:21Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no cir***stances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.
Last update was 240 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with matome-plus.net in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

qotb.ir
35 secs
qorfebazar.com
1 min
qoooq.ir
2 mins
qomweb.com
3 mins
rbq04.com
4 mins
qomsaham.blogfa.com
4 mins
qomuni.co
4 mins
qomsamak.ir
5 mins
anthropoc***gazine.org
7 mins
qompoultry.com
7 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
matome-plus.net widget