Tools & Wizards About Us
benry.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

benry.com

全国展開で生活支援サービス（便利屋）を行うベンリーです！

Page Load Speed

17.6 sec in total

First Response

919 ms

Resources Loaded

16.5 sec

Page Rendered

210 ms

benry.com screenshot

About Website

Click here to check amazing Benry content for Japan. Otherwise, check out these important facts you probably never knew about benry.com

エアコンクリーニング、ハウス・オフィスクリーニング、害虫駆除、草刈、枝切り等のお困り事なら生活支援サービス（便利屋）のベンリーが即解決。無料お見積りもございますのでお気軽にご相談ください。

Visit benry.com

Key Findings

We analyzed Benry.com page load time and found that the first response time was 919 ms and then it took 16.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

benry.com performance score

0

Network Requests Diagram

index.php

919 ms

first.css

177 ms

jquery.bxslider.css

354 ms

tipTip.css

510 ms

jquery.min.js

20 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 79% of them (66 requests) were addressed to the original Benry.com, 6% (5 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (13.3 sec) belongs to the original domain Benry.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 325.0 kB (18%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Benry.com main page is 1.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 23.9 kB

  • Original 31.2 kB
  • After minification 28.7 kB
  • After compression 7.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.9 kB or 77% of the original size.

Image Optimization

-15%

Potential reduce by 235.2 kB

  • Original 1.6 MB
  • After minification 1.3 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Benry needs image optimization as it can save up to 235.2 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-38%

Potential reduce by 64.7 kB

  • Original 170.7 kB
  • After minification 170.7 kB
  • After compression 105.9 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 64.7 kB or 38% of the original size.

CSS Optimization

-23%

Potential reduce by 1.1 kB

  • Original 4.9 kB
  • After minification 4.9 kB
  • After compression 3.8 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Benry.com needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (38%)

Requests Now

81

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Benry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

index.php

index.php

919 ms

first.css

first.css

177 ms

jquery.bxslider.css

jquery.bxslider.css

354 ms

tipTip.css

tipTip.css

510 ms

jquery.min.js

jquery.min.js

20 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

521 ms

first.js

first.js

538 ms

ga.js

ga.js

116 ms

gtm.js

gtm.js

154 ms

logo.png

logo.png

184 ms

slogan2.png

slogan2.png

183 ms

size.png

size.png

257 ms

size_01.png

size_01.png

184 ms

size_02.png

size_02.png

223 ms

size_03.png

size_03.png

459 ms

snavi_01.png

snavi_01.png

455 ms

snavi_03.png

snavi_03.png

455 ms

snavi_04.png

snavi_04.png

458 ms

snavi_05.png

snavi_05.png

457 ms

gnavi_new_01.png

gnavi_new_01.png

631 ms

gnavi_new_02.png

gnavi_new_02.png

627 ms

gnavi_new_03.png

gnavi_new_03.png

627 ms

gnavi_new_04.png

gnavi_new_04.png

617 ms

gnavi_04.png

gnavi_04.png

616 ms

pict_02.gif

pict_02.gif

13298 ms

15-1.jpg

15-1.jpg

1469 ms

14-1.png

14-1.png

959 ms

10-1.jpg

10-1.jpg

1158 ms

slide_07.jpg

slide_07.jpg

3097 ms

slide_01.jpg

slide_01.jpg

992 ms

slide_05.jpg

slide_05.jpg

1130 ms

slide_08.jpg

slide_08.jpg

1541 ms

slide_02.jpg

slide_02.jpg

1302 ms

slide_04.jpg

slide_04.jpg

1334 ms

benryfc_com.jpg

benryfc_com.jpg

1474 ms

h2_06.png

h2_06.png

1511 ms

map.png

map.png

1637 ms

icon_03.png

icon_03.png

1643 ms

icon_04.png

icon_04.png

1686 ms

icon_02.png

icon_02.png

1722 ms

h2_03.png

h2_03.png

1807 ms

h2_04.png

h2_04.png

1814 ms

gtm.js

gtm.js

215 ms

h2_05.png

h2_05.png

1860 ms

pta.js

pta.js

119 ms

h2_01.png

h2_01.png

1884 ms

icon_05.png

icon_05.png

1881 ms

__utm.gif

__utm.gif

13 ms

h2_02.png

h2_02.png

1807 ms

banner.jpg

banner.jpg

1872 ms

js

js

56 ms

js

js

249 ms

analytics.js

analytics.js

206 ms

gjo06xlsme

gjo06xlsme

244 ms

uh.js

uh.js

730 ms

bi.js

bi.js

903 ms

facebook-banner-big

facebook-banner-big

1873 ms

banner_03.png

banner_03.png

2071 ms

japan_ba.png

japan_ba.png

1904 ms

destination

destination

305 ms

collect

collect

124 ms

bg.png

bg.png

1776 ms

bg_02.png

bg_02.png

1818 ms

bg_04.png

bg_04.png

1875 ms

bg_03.png

bg_03.png

1950 ms

bx_loader.gif

bx_loader.gif

1996 ms

clarity.js

clarity.js

47 ms

collect

collect

56 ms

snavi_01_ov.png

snavi_01_ov.png

1879 ms

snavi_03_ov.png

snavi_03_ov.png

1886 ms

ga-audiences

ga-audiences

26 ms

snavi_04_ov.png

snavi_04_ov.png

1957 ms

snavi_05_ov.png

snavi_05_ov.png

2010 ms

gnavi_new_01_ov.png

gnavi_new_01_ov.png

2035 ms

gnavi_new_02_ov.png

gnavi_new_02_ov.png

1715 ms

gnavi_new_03_ov.png

gnavi_new_03_ov.png

1766 ms

gnavi_new_04_ov.png

gnavi_new_04_ov.png

1688 ms

gnavi_04_ov.png

gnavi_04_ov.png

1676 ms

icon_02_ov.png

icon_02_ov.png

1541 ms

icon_05_ov.png

icon_05_ov.png

1601 ms

controls.png

controls.png

1526 ms

small.css

small.css

178 ms

large.css

large.css

178 ms

c.gif

c.gif

7 ms

SEO Factors

benry.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Benry.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Benry.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

benry.com

Open Graph description is not detected on the main page of Benry. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: