Tools & Wizards About Us
mainline.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mainline.jp

マハブブインターナショナル合同会社

Page Load Speed

3.7 sec in total

First Response

567 ms

Resources Loaded

2.6 sec

Page Rendered

549 ms

mainline.jp screenshot

About Website

Click here to check amazing Mainline content. Otherwise, check out these important facts you probably never knew about mainline.jp

検索用文言

Visit mainline.jp

Key Findings

We analyzed Mainline.jp page load time and found that the first response time was 567 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

mainline.jp performance score

0

Network Requests Diagram

mainline.jp

567 ms

bootstrap.min.css

362 ms

font-awesome.min.css

16 ms

nivo-lightbox.css

332 ms

default.css

344 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 45% of them (35 requests) were addressed to the original Mainline.jp, 21% (16 requests) were made to Maps.google.com and 13% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Mainline.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 694.1 kB (34%)

Content Size

2.1 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mainline.jp main page is 2.1 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. 65% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 37.0 kB

  • Original 45.2 kB
  • After minification 41.9 kB
  • After compression 8.1 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 37.0 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 12.4 kB

  • Original 1.0 MB
  • After minification 1.0 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. Mainline images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 452.7 kB

  • Original 752.6 kB
  • After minification 740.6 kB
  • After compression 299.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 452.7 kB or 60% of the original size.

CSS Optimization

-85%

Potential reduce by 191.9 kB

  • Original 224.5 kB
  • After minification 192.9 kB
  • After compression 32.6 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. Mainline.jp needs all CSS files to be minified and compressed as it can save up to 191.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (51%)

Requests Now

68

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mainline.jp

mainline.jp

567 ms

bootstrap.min.css

bootstrap.min.css

362 ms

font-awesome.min.css

font-awesome.min.css

16 ms

nivo-lightbox.css

nivo-lightbox.css

332 ms

default.css

default.css

344 ms

owl.carousel.css

owl.carousel.css

346 ms

owl.theme.css

owl.theme.css

342 ms

flexslider.css

flexslider.css

369 ms

animate.css

animate.css

509 ms

style.css

style.css

515 ms

default.css

default.css

521 ms

jquery.min.js

jquery.min.js

689 ms

bootstrap.min.js

bootstrap.min.js

527 ms

jquery.sticky.js

jquery.sticky.js

602 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

677 ms

jquery.easing.min.js

jquery.easing.min.js

682 ms

jquery.scrollTo.js

jquery.scrollTo.js

710 ms

jquery.appear.js

jquery.appear.js

709 ms

stellar.js

stellar.js

732 ms

wow.min.js

wow.min.js

857 ms

owl.carousel.min.js

owl.carousel.min.js

853 ms

nivo-lightbox.min.js

nivo-lightbox.min.js

860 ms

custom.js

custom.js

861 ms

js

js

35 ms

googlemap.js

googlemap.js

880 ms

1.jpg

1.jpg

1984 ms

logo.png

logo.png

1236 ms

2.jpg

2.jpg

1838 ms

3.jpg

3.jpg

1702 ms

4.jpg

4.jpg

2026 ms

logo.jpg

logo.jpg

1086 ms

1.jpg

1.jpg

1387 ms

2.jpg

2.jpg

1531 ms

3.jpg

3.jpg

1552 ms

icon_box.png

icon_box.png

1706 ms

icon_car.png

icon_car.png

1723 ms

css

css

23 ms

css

css

35 ms

LkANqRTGviFkcUlniFHuMPesZW2xOQ-xsNqO47m55DA.ttf

LkANqRTGviFkcUlniFHuMPesZW2xOQ-xsNqO47m55DA.ttf

24 ms

9EXaIaG9EisTb0ON7WXvdZ0EAVxt0G0biEntp43Qt6E.ttf

9EXaIaG9EisTb0ON7WXvdZ0EAVxt0G0biEntp43Qt6E.ttf

25 ms

PTj8SjnLMuoZrJLoiRjMXp0EAVxt0G0biEntp43Qt6E.ttf

PTj8SjnLMuoZrJLoiRjMXp0EAVxt0G0biEntp43Qt6E.ttf

24 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

25 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

24 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

24 ms

mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf

mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf

23 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1277 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

3 ms

common.js

common.js

19 ms

map.js

map.js

19 ms

util.js

util.js

77 ms

marker.js

marker.js

76 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

341 ms

onion.js

onion.js

23 ms

openhand_8_8.cur

openhand_8_8.cur

54 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

119 ms

stats.js

stats.js

41 ms

controls.js

controls.js

33 ms

transparent.png

transparent.png

52 ms

css

css

90 ms

google4.png

google4.png

92 ms

mapcnt6.png

mapcnt6.png

51 ms

sv5.png

sv5.png

52 ms

spotlight-poi.png

spotlight-poi.png

53 ms

tmapctrl.png

tmapctrl.png

47 ms

cb_scout5.png

cb_scout5.png

52 ms

tmapctrl4.png

tmapctrl4.png

50 ms

imgs8.png

imgs8.png

51 ms

vt

vt

76 ms

vt

vt

95 ms

vt

vt

84 ms

vt

vt

108 ms

vt

vt

151 ms

vt

vt

72 ms

vt

vt

150 ms

vt

vt

146 ms

vt

vt

162 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

190 ms

SEO Factors

mainline.jp 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 Mainline.jp 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 Mainline.jp 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

mainline.jp

Open Graph description is not detected on the main page of Mainline. 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: