54 / 100
Should Fix:
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 194.9KiB (73% reduction).
- Compressing https://parts.blog.livedoor.jp/css/lite2/common.css?_v=20191201 could save 98.6KiB (82% reduction).
- Compressing https://parts.blog.livedoor.jp/js/jquery-1.11.1.min.js could save 61.1KiB (65% reduction).
- Compressing https://parts.blog.livedoor.jp/js/lite2/main.js?_v=20191201 could save 14KiB (77% reduction).
- Compressing https://parts.blog.livedoor.jp/js/lite2/common.js?_v=20191201 could save 4.7KiB (63% reduction).
- Compressing https://parts.blog.livedoor.jp/css/lite2/usr/basic2013.css?_v=20191201 could save 4.7KiB (76% reduction).
- Compressing https://parts.blog.livedoor.jp/js/c2.js?v=20191010 could save 3KiB (65% reduction).
- Compressing https://parts.blog.livedoor.jp/css/lite2/control.css?_v=20191201 could save 2.1KiB (80% reduction).
- Compressing https://parts.blog.livedoor.jp/css/lite2/usr/pager.css?_v=20191201 could save 1.9KiB (75% reduction).
- Compressing http://microad-d.openx.net/mw/1.0/acj?cc=1&ai=0ebc886c-8523-4bd2-969c-079c90cd3754&o=1488114113&callback=OX_1488114113&ju=http%3A//spotgambling.livedoor.blog/&jr=&auid=539471314&dims=412x732&adxy=56%2C1796&res=412x732x24&plg=pm&ch=UTF-8&tz=480&ws=300x250&ifr=1&tws=412x732&vmt=1&mt=1 could save 1.2KiB (61% reduction).
- Compressing https://parts.blog.livedoor.jp/js/jquery.cookie.min.js could save 1,021B (54% reduction).
- Compressing https://s-rtb.send.microadinc.com/ad?spot=cab5ac3b32153f7732a2f2ad994f4f9d&cb=microadCompass.AdRequestor.callback&url=http%3A%2F%2Fspotgambling.livedoor.blog%2F&referrer=&cbt=15148cb17c98d3016ecaa7d4e7 could save 966B (50% reduction).
- Compressing https://parts.blog.livedoor.jp/js/micro_template.js could save 806B (54% reduction).
- Compressing https://s-rtb.send.microadinc.com/ad?spot=a64b9ca7cba1aaefd9f8fe8bf8bb46e7&cb=microadCompass.AdRequestor.callback&url=http%3A%2F%2Fspotgambling.livedoor.blog%2F&referrer=http%3A%2F%2Fspotgambling.livedoor.blog%2F&cbt=210af30afc4092016ecaa7d4f4 could save 517B (41% reduction).
- Compressing http://jp-u.openx.net/w/1.0/pd?plm=10&ph=464022e2-4b47-43d2-8758-dcad4ae1fd07 could save 365B (43% reduction).
Show how to fix
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 9 blocking script resources and 4 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.
Remove render-blocking JavaScript:
- https://parts.blog.livedoor.jp/js/lite2/common.js?_v=20191201
- https://parts.blog.livedoor.jp/js/lite2/main.js?_v=20191201
- https://parts.blog.livedoor.jp/js/jquery-1.11.1.min.js
- https://parts.blog.livedoor.jp/js/jquery.cookie.min.js
- https://parts.blog.livedoor.jp/js/micro_template.js
- https://parts.blog.livedoor.jp/js/c2.js?v=20191010
- http://spotgambling.livedoor.blog/settings/lite2/ads.js
- http://js.ad-stir.com/js/nativeapi.js
- https://js.ad-stir.com/js/adstir.js?20130527
Optimize CSS Delivery of the following:
- https://parts.blog.livedoor.jp/css/lite2/common.css?_v=20191201
- https://parts.blog.livedoor.jp/css/lite2/control.css?_v=20191201
- https://parts.blog.livedoor.jp/css/lite2/usr/basic2013.css?_v=20191201
- https://parts.blog.livedoor.jp/css/lite2/usr/pager.css?_v=20191201
Show how to fix
Consider Fixing:
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:
- http://spotgambling.livedoor.blog/_/json/blog_news_sp_kind_1.json (expiration not specified)
- http://spotgambling.livedoor.blog/_/json/blog_news_sp_kind_map.json (expiration not specified)
- http://spotgambling.livedoor.blog/_/json/ranking_category_min_2.json (expiration not specified)
- http://spotgambling.livedoor.blog/settings/lite2/ads.js (expiration not specified)
- http://microad-d.openx.net/mw/1.0/jstag (60 minutes)
- https://resize.blogsys.jp/1543f8e2ed602b25ddb1a57f75bb125fa6b3edaa/crop8/124x124/https://livedoor.blogimg.jp/remmikki/imgs/e/a/ea81ead6-s.jpg (60 minutes)
- https://resize.blogsys.jp/2f35b2624737e8fda0a0e8834641b98272e6b948/crop8/124x124/https://livedoor.blogimg.jp/ske_live-apparel/imgs/6/3/63e99aba-s.jpg (60 minutes)
- https://resize.blogsys.jp/40785b1cf58cb7e9824eac284bf88de1e34db136/trim2/199x208_198p_459x283/https://livedoor.blogimg.jp/yubasan/imgs/8/e/8e402987.png (60 minutes)
- https://resize.blogsys.jp/8797e59d2f136d983ee86e2a445e765001f0e830/crop8/124x124/http://i.ytimg.com/vi/dF0YKSosqzA/hqdefault.jpg (60 minutes)
- https://resize.blogsys.jp/f6944cbc08ef54270c0cb6933d57b15e3ac81822/crop8/124x124/https://livedoor.blogimg.jp/tenbaihakase/imgs/8/e/8e5aef91-s.jpg (60 minutes)
- https://t.blog.livedoor.jp/u.js (60 minutes)
Show how to fix
Reduce server response time
In our test, your server responded in 0.35 seconds.
There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
Show how to fix
Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 18.6KiB (15% reduction).
- Minifying https://parts.blog.livedoor.jp/css/lite2/common.css?_v=20191201 could save 16.7KiB (14% reduction).
- Minifying https://parts.blog.livedoor.jp/css/lite2/usr/basic2013.css?_v=20191201 could save 1.3KiB (22% reduction).
- Minifying https://parts.blog.livedoor.jp/css/lite2/usr/pager.css?_v=20191201 could save 653B (26% reduction).
Show how to fix
Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 10.7KiB (32% reduction).
- Minifying https://parts.blog.livedoor.jp/js/lite2/main.js?_v=20191201 could save 6.1KiB (34% reduction).
- Minifying https://parts.blog.livedoor.jp/js/lite2/common.js?_v=20191201 could save 2.5KiB (34% reduction).
- Minifying https://parts.blog.livedoor.jp/js/c2.js?v=20191010 could save 1,018B (22% reduction).
- Minifying https://parts.blog.livedoor.jp/js/micro_template.js could save 866B (58% reduction).
- Minifying http://microad-d.openx.net/mw/1.0/acj?cc=1&ai=0ebc886c-8523-4bd2-969c-079c90cd3754&o=1488114113&callback=OX_1488114113&ju=http%3A//spotgambling.livedoor.blog/&jr=&auid=539471314&dims=412x732&adxy=56%2C1796&res=412x732x24&plg=pm&ch=UTF-8&tz=480&ws=300x250&ifr=1&tws=412x732&vmt=1&mt=1 could save 230B (12% reduction).
Show how to fix
Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 12.8KiB (43% reduction).
- Compressing https://resize.blogsys.jp/1543f8e2ed602b25ddb1a57f75bb125fa6b3edaa/crop8/124x124/https://livedoor.blogimg.jp/remmikki/imgs/e/a/ea81ead6-s.jpg could save 3KiB (45% reduction).
- Compressing https://resize.blogsys.jp/2f35b2624737e8fda0a0e8834641b98272e6b948/crop8/124x124/https://livedoor.blogimg.jp/ske_live-apparel/imgs/6/3/63e99aba-s.jpg could save 2.8KiB (42% reduction).
- Compressing https://resize.blogsys.jp/8797e59d2f136d983ee86e2a445e765001f0e830/crop8/124x124/http://i.ytimg.com/vi/dF0YKSosqzA/hqdefault.jpg could save 2.7KiB (46% reduction).
- Compressing https://resize.blogsys.jp/f6944cbc08ef54270c0cb6933d57b15e3ac81822/crop8/124x124/https://livedoor.blogimg.jp/tenbaihakase/imgs/8/e/8e5aef91-s.jpg could save 2.1KiB (42% reduction).
- Compressing https://parts.blog.livedoor.jp/img/lite2/noimage_s.png could save 1KiB (28% reduction).
- Compressing https://parts.blog.livedoor.jp/img/lite2/arrow_pull.png could save 874B (72% reduction).
- Compressing https://parts.blog.livedoor.jp/img/lite2/icon_pager_first.png could save 236B (43% reduction).
- Compressing https://parts.blog.livedoor.jp/img/lite2/icon_pager_last.png could save 219B (40% reduction).
Show how to fix
3 Passed Rules
100 / 100
5 Passed Rules
Show details
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.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
65 / 100
Should Fix:
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 249.3KiB (67% reduction).
- Compressing https://clap.blogcms.jp/js/jquery-1.11.1.min.js could save 61.1KiB (65% reduction).
- Compressing https://parts.blog.livedoor.jp/js/jquery-1.11.1.min.js could save 61.1KiB (65% reduction).
- Compressing https://parts.blog.livedoor.jp/js/jquery-1.7.1.min.js could save 59.3KiB (64% reduction).
- Compressing https://parts.blog.livedoor.jp/css/template.css?v=20190826 could save 32KiB (79% reduction).
- Compressing https://parts.blog.livedoor.jp/css/template_6thgen.css could save 16.9KiB (76% reduction).
- Compressing http://spotgambling.livedoor.blog/settings/header.js?v=20190705 could save 7.3KiB (73% reduction).
- Compressing https://parts.blog.livedoor.jp/js/c2.js?v=20191010 could save 3KiB (65% reduction).
- Compressing https://parts.blog.livedoor.jp/js/design.js could save 2.3KiB (64% reduction).
- Compressing https://clap.blogcms.jp/img/clap_icon.svg could save 2.1KiB (61% reduction).
- Compressing https://clap.blogcms.jp/livedoor/spotgambling/4471584/button could save 1.7KiB (58% reduction).
- Compressing https://parts.blog.livedoor.jp/js/smartphone.js?v=20131007 could save 1.1KiB (57% reduction).
- Compressing https://parts.blog.livedoor.jp/css/comment2/heart.css?v=20180704 could save 701B (65% reduction).
- Compressing https://parts.blog.livedoor.jp/css/comment2/icon.css?v=20180704 could save 690B (61% reduction).
Show how to fix
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 8 blocking script resources and 5 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.
Remove render-blocking JavaScript:
- https://parts.blog.livedoor.jp/js/jquery-1.11.1.min.js
- https://parts.blog.livedoor.jp/js/usr/import.js
- https://parts.blog.livedoor.jp/js/jquery-1.7.1.min.js
- https://parts.blog.livedoor.jp/js/design.js
- https://parts.blog.livedoor.jp/js/c2.js?v=20191010
- https://parts.blog.livedoor.jp/js/smartphone.js?v=20131007
- http://spotgambling.livedoor.blog/settings/header.js?v=20190705
- http://spotgambling.livedoor.blog/settings/ad.js
Optimize CSS Delivery of the following:
- https://parts.blog.livedoor.jp/css/template.css?v=20190826
- https://parts.blog.livedoor.jp/css/comment2/heart.css?v=20180704
- https://parts.blog.livedoor.jp/css/comment2/icon.css?v=20180704
- http://spotgambling.livedoor.blog/site.css?_=20191115195246
- https://parts.blog.livedoor.jp/css/template_6thgen.css
Show how to fix
Consider Fixing:
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:
- http://spotgambling.livedoor.blog/settings/ad.js (expiration not specified)
- https://clap.blogcms.jp/img/clap_icon.svg (expiration not specified)
- https://clap.blogcms.jp/js/jquery-1.11.1.min.js (expiration not specified)
- https://secure.livechatinc.com/licence/11352022/v2/get_static_config.0.81.1.1.42.9.21.1.1.3.1.2.18.js?&jsonp=__lc_data_static_config (8.9 minutes)
- https://secure.livechatinc.com/licence/11352022/v2/localization.id.0.b2f6bac2deeb36d88973d9bb7e9b03b8_eb2937685d8deafb898c109270429fc6.js?acao=true (9.8 minutes)
- https://syndication.twitter.com/settings (10 minutes)
- https://platform.twitter.com/widgets.js (30 minutes)
- http://spotgambling.livedoor.blog/logo.png (60 minutes)
- https://t.blog.livedoor.jp/u.js (60 minutes)
- https://cdn.livechatinc.com/tracking.js (8 hours)
Show how to fix
Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 14KiB (21% reduction).
- Minifying https://parts.blog.livedoor.jp/css/template.css?v=20190826 could save 8.6KiB (22% reduction).
- Minifying https://parts.blog.livedoor.jp/css/template_6thgen.css could save 4KiB (19% reduction).
- Minifying http://spotgambling.livedoor.blog/site.css?_=20191115195246 could save 1.1KiB (27% reduction) after compression.
- Minifying https://parts.blog.livedoor.jp/css/comment2/icon.css?v=20180704 could save 233B (21% reduction).
- Minifying https://parts.blog.livedoor.jp/css/comment2/heart.css?v=20180704 could save 125B (12% reduction).
Show how to fix
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 parse times.
Minify HTML for the following resources to reduce their size by 1.6KiB (15% reduction).
- Minifying http://spotgambling.livedoor.blog/ could save 1.1KiB (14% reduction) after compression.
- Minifying https://clap.blogcms.jp/livedoor/spotgambling/4471584/button could save 538B (19% reduction).
Show how to fix
Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 4.9KiB (25% reduction).
- Minifying http://spotgambling.livedoor.blog/settings/header.js?v=20190705 could save 2.5KiB (25% reduction).
- Minifying https://parts.blog.livedoor.jp/js/c2.js?v=20191010 could save 1,018B (22% reduction).
- Minifying https://parts.blog.livedoor.jp/js/design.js could save 895B (25% reduction).
- Minifying https://parts.blog.livedoor.jp/js/smartphone.js?v=20131007 could save 584B (29% reduction).
Show how to fix
Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 57KiB (50% reduction).
- Compressing https://1.bp.blogspot.com/-R-w8NZCfD8I/XeUV8rifDlI/AAAAAAAACFI/Q-3LTlrCNrwB4JWYfr9PA6qZWTzykwSrgCEwYBhgL/s640/judislot185.jpg could save 51.8KiB (50% reduction).
- Compressing https://parts.blog.livedoor.jp/img/usr/cmn/logo_blog_premium.png could save 1KiB (28% reduction).
- Compressing https://parts.blog.livedoor.jp/img/usr/default_2012/common/to_pagetop.png could save 1KiB (52% reduction).
- Compressing https://parts.blog.livedoor.jp/img/usr/ver06_km_contrastive_2c/icon_next_end.png could save 944B (90% reduction).
- Compressing https://parts.blog.livedoor.jp/img/usr/ver06_km_contrastive_2c/list.png could save 923B (91% reduction).
- Compressing https://parts.blog.livedoor.jp/img/usr/ver06_km_contrastive_2c/icon_next.png could save 921B (90% reduction).
- Compressing https://static.xx.fbcdn.net/rsrc.php/v3/y5/r/OqOE21UvWe3.png could save 201B (50% reduction).
- Compressing https://parts.blog.livedoor.jp/img/user_blog/livedoor/entry_icon.png could save 145B (48% reduction).
- Compressing https://parts.blog.livedoor.jp/img/user_blog/livedoor/calendar_icon.png could save 132B (51% reduction).
Show how to fix
3 Passed Rules
* The results are cached for 30s. If you have made changes to your page, please wait for 30s before re-running the test.