Erozine.Tokyo - Info erozine.tokyo

erozine.tokyo receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank erozine.tokyo is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in Osaka, Ōsaka, 543-0062, Japan and links to network IP address 153.120.181.220. This server supports HTTPS and HTTP/2.

About - erozine.tokyo


Technologies used on Website

Font Scripts
Font Awesome
Analytics
Google Analytics
Web Servers
LiteSpeed
Programming Languages
PHP
JavaScript Libraries
Slick
jQuery
CMS
WordPress
Blogs
WordPress
Databases
MySQL

erozine.tokyo Profile

Title: EROzine.tokyo
Last update was 8 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with erozine.tokyo in any way. Only publicly available statistics data are displayed.

How popular is erozine.tokyo?

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Unique Visitors:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
00:00
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  erozine.tokyo
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 erozine.tokyo?

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:
erozine.tokyo
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:
erozine.tokyo
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 erozine.tokyo can earn?

Daily Revenue:
n/a
Monthly Revenue:
n/a
Yearly Revenue:
n/a
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do erozine.tokyo lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is erozine.tokyo worth?

Website Value:
n/a

+ Where is erozine.tokyo hosted?

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

Other sites hosted on 153.120.181.220

+ How fast does erozine.tokyo load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

98
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

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.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. 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.
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.
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.7 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.7 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.7 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.

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

URL
SizePotential Savings
http://erozine.tokyo/wp-content/themes/affinger5/css/normalize.css?ver=1.5.9
1 KB70
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome.min.css?ver=4.7.0
7 KB150
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome-animation.min.css?ver=4.9.10
2 KB110
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/style.css?ver=4.9.10
1 KB110
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.css?ver=1.8.0
1 KB110
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick-theme.css?ver=1.8.0
1 KB110
http://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
29 KB190
http://erozine.tokyo/wp-content/themes/affinger5-child/style.css?ver=4.9.10
1 KB70
http://erozine.tokyo/wp-content/themes/affinger5/st-rankcss.php
3 KB70
http://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js?ver=1.11.3
33 KB270
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://erozine.tokyo/
0 ms254 ms6 KB19 KB200text/htmlDocument
http://erozine.tokyo/wp-content/themes/affinger5/css/normalize.css?ver=1.5.9
267 ms443 ms1 KB2 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome.min.css?ver=4.7.0
267 ms444 ms7 KB30 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome-animation.min.css?ver=4.9.10
267 ms636 ms2 KB18 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/style.css?ver=4.9.10
268 ms444 ms1 KB2 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.css?ver=1.8.0
268 ms444 ms1 KB2 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick-theme.css?ver=1.8.0
268 ms446 ms1 KB3 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
268 ms628 ms29 KB163 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5-child/style.css?ver=4.9.10
269 ms446 ms1 KB1 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/st-rankcss.php
269 ms510 ms3 KB15 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/st-themecss-loader.php?ver=4.9.10
269 ms571 ms9 KB43 KB200text/cssStylesheet
http://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js?ver=1.11.3
269 ms276 ms33 KB94 KB200text/javascriptScript
https://erozine.tokyo/wp-content/uploads/2019/04/erozine_logo.png
270 ms809 ms5 KB4 KB200image/pngImage
https://erozine.tokyo/wp-content/uploads/2017/11/sample_gazou-150x150.png
270 ms627 ms17 KB16 KB200image/pngImage
http://b.st-hatena.com/js/bookmark_button.js
670 ms774 ms1 KB0 KB301text/html
http://erozine.tokyo/wp-content/themes/affinger5/images/search.png
670 ms859 ms1 KB0 KB200image/pngImage
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.js?ver=1.5.9
629 ms809 ms15 KB86 KB200application/javascriptScript
http://erozine.tokyo/wp-content/themes/affinger5/js/base.js?ver=4.9.10
669 ms847 ms3 KB12 KB200application/javascriptScript
http://erozine.tokyo/wp-content/themes/affinger5/js/scroll.js?ver=4.9.10
669 ms858 ms1 KB1 KB200application/javascriptScript
http://erozine.tokyo/wp-content/themes/affinger5/js/st-copy-text.js?ver=4.9.10
270 ms773 ms0 KB0 KB-1Script
http://erozine.tokyo/wp-includes/js/wp-embed.min.js?ver=4.9.10
670 ms859 ms1 KB1 KB200application/javascriptScript
http://erozine.tokyo/wp-includes/js/wp-emoji-release.min.js?ver=4.9.10
670 ms859 ms4 KB12 KB200application/javascriptScript
http://www.google-analytics.com/analytics.js
667 ms773 ms0 KB0 KB-1Script
http://erozine.tokyo/wp-content/themes/affinger5/st-themecss-loader.php?ver=4.9.10
680 ms965 ms9 KB43 KB200text/cssImage
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/fonts/fontawesome-webfont.woff2?v=4.7.0
686 ms1055 ms76 KB75 KB200font/woff2Font
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/fonts/stsvg.ttf?poe1v2
686 ms865 ms3 KB3 KB200font/ttfFont
https://b.st-hatena.com/js/bookmark_button.js
774 ms818 ms11 KB34 KB200application/x-javascriptScript
https://api.b.st-hatena.com/entry/button/?url=http%3A%2F%2Ferozine.tokyo%2F&layout=simple&format=image
848 ms929 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 21 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/fonts/fontawesome-webfont.woff2?v=4.7.0
0 ms76 KB
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/fonts/stsvg.ttf?poe1v2
0 ms3 KB
https://api.b.st-hatena.com/entry/button/?url=http%3A%2F%2Ferozine.tokyo%2F&layout=simple&format=image
3600000 ms0 KB
https://b.st-hatena.com/js/bookmark_button.js
86400000 ms11 KB
http://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
604800000 ms29 KB
https://erozine.tokyo/wp-content/uploads/2017/11/sample_gazou-150x150.png
604800000 ms17 KB
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.js?ver=1.5.9
604800000 ms15 KB
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome.min.css?ver=4.7.0
604800000 ms7 KB
https://erozine.tokyo/wp-content/uploads/2019/04/erozine_logo.png
604800000 ms5 KB
http://erozine.tokyo/wp-includes/js/wp-emoji-release.min.js?ver=4.9.10
604800000 ms4 KB
http://erozine.tokyo/wp-content/themes/affinger5/js/base.js?ver=4.9.10
604800000 ms3 KB
http://erozine.tokyo/wp-content/themes/affinger5/st-rankcss.php
604800000 ms3 KB
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome-animation.min.css?ver=4.9.10
604800000 ms2 KB
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick-theme.css?ver=1.8.0
604800000 ms1 KB
http://erozine.tokyo/wp-content/themes/affinger5/css/normalize.css?ver=1.5.9
604800000 ms1 KB
http://erozine.tokyo/wp-includes/js/wp-embed.min.js?ver=4.9.10
604800000 ms1 KB
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/style.css?ver=4.9.10
604800000 ms1 KB
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.css?ver=1.8.0
604800000 ms1 KB
http://erozine.tokyo/wp-content/themes/affinger5/js/scroll.js?ver=4.9.10
604800000 ms1 KB
http://erozine.tokyo/wp-content/themes/affinger5-child/style.css?ver=4.9.10
604800000 ms1 KB
http://erozine.tokyo/wp-content/themes/affinger5/images/search.png
604800000 ms1 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
33 KB0 ms
12 KB0 ms
0 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
277 ms
7 ms
287 ms
57 ms
652 ms
8 ms
662 ms
32 ms
694 ms
99 ms
797 ms
50 ms
852 ms
5 ms
862 ms
7 ms
884 ms
27 ms
912 ms
17 ms
930 ms
7 ms
1077 ms
37 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/fonts/fontawesome-webfont.woff2?v=4.7.0
369 ms
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/fonts/stsvg.ttf?poe1v2
178 ms
JavaScript execution time - 0.1 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
267 ms6 ms1 ms
http://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js?ver=1.11.3
60 ms53 ms2 ms
http://erozine.tokyo/
52 ms50 ms2 ms
Minify CSS - Potential savings of 11 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
http://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
29 KB7 KB
http://erozine.tokyo/wp-content/themes/affinger5/st-themecss-loader.php?ver=4.9.10
9 KB3 KB
Remove unused CSS - Potential savings of 26 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://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
29 KB26 KB
Avoids enormous network payloads - Total size was 238 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/fonts/fontawesome-webfont.woff2?v=4.7.0
76 KB
http://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js?ver=1.11.3
33 KB
http://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
29 KB
https://erozine.tokyo/wp-content/uploads/2017/11/sample_gazou-150x150.png
17 KB
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.js?ver=1.5.9
15 KB
https://b.st-hatena.com/js/bookmark_button.js
11 KB
http://erozine.tokyo/wp-content/themes/affinger5/st-themecss-loader.php?ver=4.9.10
9 KB
http://erozine.tokyo/wp-content/themes/affinger5/st-themecss-loader.php?ver=4.9.10
9 KB
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome.min.css?ver=4.7.0
7 KB
http://erozine.tokyo/
6 KB
Minimizes main-thread work - 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
172 ms
Script Evaluation
126 ms
Other
62 ms
Parse HTML & CSS
26 ms
Rendering
18 ms
Script Parsing & Compilation
12 ms
Serve images in next-gen formats - Potential savings of 13 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
https://erozine.tokyo/wp-content/uploads/2017/11/sample_gazou-150x150.png
16 KB13 KB
Avoids an excessive DOM size - 150 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). Learn more.

Statistic
ElementValue
Total DOM Elements
150
Maximum DOM Depth
16
Maximum Child Elements
10
Minify JavaScript - Potential savings of 9 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.js?ver=1.5.9
15 KB6 KB
https://b.st-hatena.com/js/bookmark_button.js
11 KB3 KB
Keep request counts low and transfer sizes small - 28 requests • 238 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
28238 KB
Font
278 KB
Script
968 KB
Stylesheet
1054 KB
Image
531 KB
Document
16 KB
Other
11 KB
Media
00 KB
Third-party
545 KB
Server response times are low (TTFB) - Root document took 250 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. 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.

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.

Avoid chaining critical requests - 18 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. 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.


Page Speed (Google PageSpeed Insights) - Mobile

93
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

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 2.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 100 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 2.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. 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.
First Contentful Paint (3G) 4444.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 3.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.4 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 2.3 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 47 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
https://erozine.tokyo/wp-content/uploads/2017/11/sample_gazou-300x300.png
54 KB47 KB
Avoids an excessive DOM size - 131 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). Learn more.

Statistic
ElementValue
Total DOM Elements
131
Maximum DOM Depth
16
Maximum Child Elements
9
Minify JavaScript - Potential savings of 9 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.js?ver=1.5.9
15 KB6 KB
https://b.st-hatena.com/js/bookmark_button.js
11 KB3 KB
Keep request counts low and transfer sizes small - 28 requests • 294 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
28294 KB
Script
886 KB
Font
278 KB
Image
670 KB
Stylesheet
1053 KB
Document
16 KB
Other
11 KB
Media
00 KB
Third-party
663 KB
Eliminate render-blocking resources - Potential savings of 1,370 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://erozine.tokyo/wp-content/themes/affinger5/css/normalize.css?ver=1.5.9
1 KB180
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome.min.css?ver=4.7.0
7 KB630
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome-animation.min.css?ver=4.9.10
2 KB330
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/style.css?ver=4.9.10
1 KB330
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.css?ver=1.8.0
1 KB330
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick-theme.css?ver=1.8.0
1 KB330
http://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
29 KB780
http://erozine.tokyo/wp-content/themes/affinger5/st-rankcss.php
3 KB330
http://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js?ver=1.11.3
33 KB1230
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://erozine.tokyo/
0 ms455 ms6 KB17 KB200text/htmlDocument
http://erozine.tokyo/wp-content/themes/affinger5/css/normalize.css?ver=1.5.9
468 ms645 ms1 KB2 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome.min.css?ver=4.7.0
468 ms860 ms7 KB30 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome-animation.min.css?ver=4.9.10
468 ms997 ms2 KB18 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/style.css?ver=4.9.10
468 ms643 ms1 KB2 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.css?ver=1.8.0
469 ms850 ms1 KB2 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick-theme.css?ver=1.8.0
469 ms843 ms1 KB3 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
469 ms1027 ms29 KB163 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5-child/style.css?ver=4.9.10
469 ms540 ms0 KB0 KB-1Stylesheet
http://erozine.tokyo/wp-content/themes/affinger5/st-rankcss.php
470 ms897 ms3 KB15 KB200text/cssStylesheet
http://erozine.tokyo/wp-content/themes/affinger5/st-themecss-loader.php?ver=4.9.10
470 ms735 ms9 KB43 KB200text/cssStylesheet
http://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js?ver=1.11.3
470 ms477 ms33 KB94 KB200text/javascriptScript
https://erozine.tokyo/wp-content/uploads/2019/04/erozine_logo.png
470 ms651 ms5 KB4 KB200image/pngImage
https://erozine.tokyo/wp-content/uploads/2017/11/sample_gazou-300x300.png
470 ms1349 ms54 KB54 KB200image/pngImage
http://b.st-hatena.com/js/bookmark_button.js
1058 ms1132 ms1 KB0 KB301text/html
http://erozine.tokyo/wp-content/themes/affinger5/images/search.png
1058 ms1258 ms1 KB0 KB200image/pngImage
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.js?ver=1.5.9
652 ms1020 ms15 KB86 KB200application/javascriptScript
http://erozine.tokyo/wp-content/themes/affinger5/js/base.js?ver=4.9.10
1022 ms1197 ms3 KB12 KB200application/javascriptScript
http://erozine.tokyo/wp-content/themes/affinger5/js/st-copy-text.js?ver=4.9.10
1058 ms1237 ms1 KB2 KB200application/javascriptScript
http://erozine.tokyo/wp-includes/js/wp-embed.min.js?ver=4.9.10
1058 ms1236 ms1 KB1 KB200application/javascriptScript
http://erozine.tokyo/wp-includes/js/wp-emoji-release.min.js?ver=4.9.10
1058 ms1235 ms4 KB12 KB200application/javascriptScript
http://www.google-analytics.com/analytics.js
1058 ms1064 ms18 KB43 KB200text/javascriptScript
http://erozine.tokyo/wp-content/themes/affinger5/st-themecss-loader.php?ver=4.9.10
1066 ms1304 ms9 KB43 KB200text/cssImage
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/fonts/fontawesome-webfont.woff2?v=4.7.0
1071 ms1596 ms76 KB75 KB200font/woff2Font
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/fonts/stsvg.ttf?poe1v2
1072 ms1247 ms3 KB3 KB200font/ttfFont
https://b.st-hatena.com/js/bookmark_button.js
1132 ms1159 ms11 KB34 KB200application/x-javascriptScript
http://www.google-analytics.com/r/collect?v=1&_v=j79&a=1055705003&t=pageview&_s=1&dl=http%3A%2F%2Ferozine.tokyo%2F&ul=en-us&de=UTF-8&dt=EROzine.tokyo&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAEAB~&jid=412425102&gjid=763766808&cid=24572917.1573263439&tid=UA-109148962-1&_gid=1782185859.1573263439&_r=1&z=1461621709
1198 ms1203 ms0 KB0 KB200image/gifImage
https://api.b.st-hatena.com/entry/button/?url=http%3A%2F%2Ferozine.tokyo%2F&layout=simple&format=image
1203 ms1227 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 21 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/fonts/fontawesome-webfont.woff2?v=4.7.0
0 ms76 KB
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/fonts/stsvg.ttf?poe1v2
0 ms3 KB
https://api.b.st-hatena.com/entry/button/?url=http%3A%2F%2Ferozine.tokyo%2F&layout=simple&format=image
3600000 ms0 KB
http://www.google-analytics.com/analytics.js
7200000 ms18 KB
https://b.st-hatena.com/js/bookmark_button.js
86400000 ms11 KB
https://erozine.tokyo/wp-content/uploads/2017/11/sample_gazou-300x300.png
604800000 ms54 KB
http://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
604800000 ms29 KB
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.js?ver=1.5.9
604800000 ms15 KB
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome.min.css?ver=4.7.0
604800000 ms7 KB
https://erozine.tokyo/wp-content/uploads/2019/04/erozine_logo.png
604800000 ms5 KB
http://erozine.tokyo/wp-includes/js/wp-emoji-release.min.js?ver=4.9.10
604800000 ms4 KB
http://erozine.tokyo/wp-content/themes/affinger5/js/base.js?ver=4.9.10
604800000 ms3 KB
http://erozine.tokyo/wp-content/themes/affinger5/st-rankcss.php
604800000 ms3 KB
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome-animation.min.css?ver=4.9.10
604800000 ms2 KB
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick-theme.css?ver=1.8.0
604800000 ms1 KB
http://erozine.tokyo/wp-content/themes/affinger5/css/normalize.css?ver=1.5.9
604800000 ms1 KB
http://erozine.tokyo/wp-content/themes/affinger5/js/st-copy-text.js?ver=4.9.10
604800000 ms1 KB
http://erozine.tokyo/wp-includes/js/wp-embed.min.js?ver=4.9.10
604800000 ms1 KB
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/style.css?ver=4.9.10
604800000 ms1 KB
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.css?ver=1.8.0
604800000 ms1 KB
http://erozine.tokyo/wp-content/themes/affinger5/images/search.png
604800000 ms1 KB
Minimize third-party usage - Third-party code blocked the main thread for 60 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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
18 KB41 ms
33 KB17 ms
12 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
479 ms
7 ms
488 ms
73 ms
1049 ms
7 ms
1056 ms
25 ms
1082 ms
70 ms
1155 ms
34 ms
1194 ms
25 ms
1261 ms
18 ms
1280 ms
8 ms
1618 ms
18 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/fonts/fontawesome-webfont.woff2?v=4.7.0
525 ms
http://erozine.tokyo/wp-content/themes/affinger5/st_svg/fonts/stsvg.ttf?poe1v2
176 ms
Minify CSS - Potential savings of 11 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
http://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
29 KB7 KB
http://erozine.tokyo/wp-content/themes/affinger5/st-themecss-loader.php?ver=4.9.10
9 KB3 KB
JavaScript execution time - 0.5 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
867 ms17 ms4 ms
http://erozine.tokyo/
274 ms268 ms7 ms
http://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js?ver=1.11.3
128 ms111 ms8 ms
http://www.google-analytics.com/analytics.js
100 ms93 ms6 ms
Remove unused CSS - Potential savings of 27 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://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
29 KB27 KB
Avoids enormous network payloads - Total size was 294 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/fonts/fontawesome-webfont.woff2?v=4.7.0
76 KB
https://erozine.tokyo/wp-content/uploads/2017/11/sample_gazou-300x300.png
54 KB
http://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js?ver=1.11.3
33 KB
http://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10
29 KB
http://www.google-analytics.com/analytics.js
18 KB
http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.js?ver=1.5.9
15 KB
https://b.st-hatena.com/js/bookmark_button.js
11 KB
http://erozine.tokyo/wp-content/themes/affinger5/st-themecss-loader.php?ver=4.9.10
9 KB
http://erozine.tokyo/wp-content/themes/affinger5/st-themecss-loader.php?ver=4.9.10
9 KB
http://erozine.tokyo/wp-content/themes/affinger5/css/fontawesome/css/font-awesome.min.css?ver=4.7.0
7 KB
Minimizes main-thread work - 1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
521 ms
Style & Layout
483 ms
Other
230 ms
Parse HTML & CSS
103 ms
Rendering
70 ms
Script Parsing & Compilation
45 ms
Avoid chaining critical requests - 17 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. 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 460 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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

Efficiently encode images
Optimized images load faster and consume less cellular data. 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.

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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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://erozine.tokyo/wp-content/themes/affinger5/css/normalize.css?ver=1.5.9

Optimize images

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

Optimize the following images to reduce their size by 17.7KiB (31% reduction).

Compressing https://erozine.tokyo/wp-content/uploads/2017/11/sample_gazou-300x300.png could save 15.1KiB (28% reduction).
Compressing https://erozine.tokyo/wp-content/uploads/2019/04/erozine_logo.png could save 2.6KiB (57% 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 14.3KiB (35% reduction).

Minifying http://erozine.tokyo/wp-content/themes/affinger5/style.css?ver=4.9.10 could save 9.5KiB (32% reduction) after compression.
Minifying http://erozine.tokyo/wp-content/themes/affinger5/st-themecss-loader.php?ver=4.9.10 could save 3.5KiB (44% reduction) after compression.
Minifying http://erozine.tokyo/wp-content/themes/affinger5/st-rankcss.php could save 989B (36% reduction) after compression.
Minifying http://erozine.tokyo/wp-content/themes/affinger5-child/style.css?ver=4.9.10 could save 322B (76% reduction) after compression.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://api.b.st-hatena.com/entry/button/?url=http%3A%2F%2Ferozine.tokyo%2F&layout=simple&format=image (60 minutes)
http://www.google-***ytics.com/***ytics.js (2 hours)

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 <input id="s" type="text" name="s"> is close to 2 other tap targets.
The tap target <input id="searchsubmit" type="image"> is close to 1 other tap targets.
The tap target <a href="https://erozine.tokyo">ホーム</a> is close to 1 other tap targets.
The tap target <a href="https://erozine.tokyo">ホーム</a> is close to 1 other tap targets.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 5.4KiB (24% reduction).

Minifying http://erozine.tokyo/wp-content/themes/affinger5/vendor/slick/slick.js?ver=1.5.9 could save 3.6KiB (25% reduction) after compression.
Minifying https://b.st-hatena.com/js/bookmark_button.js could save 1.8KiB (21% reduction) after compression.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 873B (16% reduction).

Minifying http://erozine.tokyo/ could save 873B (16% reduction) after compression.
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.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
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.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does erozine.tokyo use compression?

erozine.tokyo use br compression.
Original size: 18.84 KB
Compressed size: 5.78 KB
File reduced by: 13.06 KB (69%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

erozine.tokyo supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: erozine.tokyo
Organization:
Location:
Issuer: cPanel, Inc. Certification Authority
Valid from: Sep 19 00:00:00 2019 GMT
Valid until: Dec 18 23:59:59 2019 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

erozine.tokyo supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

X-Powered-By: PHP/7.0.33
Content-Type: text/html; charset=UTF-8
Link: <https://erozine.tokyo/wp-json/>; rel="https://api.w.org/"
Transfer-Encoding: chunked
Content-Encoding: br
Vary: Accept-Encoding
Date: Sat, 09 Nov 2019 01:37:04 GMT
Server: LiteSpeed
Connection: Keep-Alive

+ DNS Lookup

Type Ip Target TTL
TXT 571
MX erozine.tokyo 571
SOA 3571
Mname ns1.mixhost.jp
Rname system.mixhost.info
Serial Number 2019042003
Refresh 3600
Retry 7200
Expire 1209600
Minimum TTL 0
A 153.120.181.220 571
NS ns2.mixhost.jp 3571
NS ns1.mixhost.jp 3571

+ Whois Lookup

Domain Created:
2019-04-20
Domain Age:
6 months 18 days  
WhoIs:
 

whois lookup at whois.nic.tokyo...
Domain Name: EROZINE.TOKYO
Registry Domain ID: DO4239130-GMO
Registrar WHOIS Server:
Registrar URL: http://www.onamae.com/
Updated Date: 2019-06-03T02:35:45.0Z
Creation Date: 2019-04-20T03:47:00.0Z
Registry Expiry Date: 2020-04-20T23:59:59.0Z
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
Registrant State/Province: ***uoka
Registrant Country: JP
Registrant Email:
Admin Email:
Tech Email:
Name Server: NS1.MIXHOST.JP
Name Server: NS2.MIXHOST.JP
Name Server: NS3.MIXHOST.JP
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-11-09T01:37:31.0Z <<<

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

Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

This whois service is provided by GMO Registry and only contains
information pertaining to Internet domain names we have registered for
our customers. By using this service you are agreeing (1) not to use any
information presented here for any purpose other than determining
ownership of domain names, (2) not to store or reproduce this data in
any way, (3) not to use any high-volume, automated, electronic processes
to obtain data from this service. Abuse of this service is monitored and
actions in contravention of these terms will result in being permanently
blacklisted. All data is (c) GMO Registry http://www.gmo-registry.com/en/
Last update was 8 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with erozine.tokyo in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

indo***.net
4 secs
bytbox.viasat.se
16 secs
pourhub.com
17 secs
hyung86.deviantart.com
20 secs
***pad.net
22 secs
buyphibian.com
28 secs
bweb.aon.at
52 secs
hypjobs.ca
1 min
bwlcloud.org
1 min
fcorp-acronym-database.uptodown.com
1 min

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!
erozine.tokyo widget