Tools & Wizards About Us
magepaipu.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

magepaipu.com

『曲げパイプ.com』自動車マフラーパーツ卸通信販売

Page Load Speed

6.3 sec in total

First Response

794 ms

Resources Loaded

5.3 sec

Page Rendered

208 ms

magepaipu.com screenshot

About Website

Welcome to magepaipu.com homepage info - get ready to check Magepaipu best content right away, or after learning these important things about magepaipu.com

自動車マフラーパーツ卸通信販売を行っております

Visit magepaipu.com

Key Findings

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

Performance Metrics

magepaipu.com performance score

0

Network Requests Diagram

magepaipu.com

794 ms

import.css

309 ms

script.js

358 ms

check_history.css

311 ms

pager.css

335 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 59% of them (54 requests) were addressed to the original Magepaipu.com, 16% (15 requests) were made to S-j-k.net and 3% (3 requests) were made to Sync.fout.jp. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Magepaipu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 101.1 kB (36%)

Content Size

281.7 kB

After Optimization

180.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 54.8 kB

  • Original 64.4 kB
  • After minification 51.1 kB
  • After compression 9.6 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. This page needs HTML code to be minified as it can gain 13.3 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 54.8 kB or 85% of the original size.

Image Optimization

-11%

Potential reduce by 19.0 kB

  • Original 180.7 kB
  • After minification 161.7 kB

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, Magepaipu needs image optimization as it can save up to 19.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-56%

Potential reduce by 5.0 kB

  • Original 9.0 kB
  • After minification 7.1 kB
  • After compression 4.0 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 5.0 kB or 56% of the original size.

CSS Optimization

-81%

Potential reduce by 22.3 kB

  • Original 27.7 kB
  • After minification 22.6 kB
  • After compression 5.4 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. Magepaipu.com needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (39%)

Requests Now

88

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

magepaipu.com

magepaipu.com

794 ms

import.css

import.css

309 ms

script.js

script.js

358 ms

check_history.css

check_history.css

311 ms

pager.css

pager.css

335 ms

shopdetail.css

shopdetail.css

339 ms

ranking.css

ranking.css

357 ms

basket.css

basket.css

361 ms

security.css

security.css

384 ms

category_menu.css

category_menu.css

646 ms

topicpath.css

topicpath.css

686 ms

catalog.css

catalog.css

688 ms

count3.makeshop.jp

count3.makeshop.jp

333 ms

infura.gif

infura.gif

699 ms

blog2.gif

blog2.gif

720 ms

categorybar.gif

categorybar.gif

575 ms

c1.gif

c1.gif

574 ms

c2.gif

c2.gif

581 ms

c3.gif

c3.gif

588 ms

c4.gif

c4.gif

762 ms

c5.gif

c5.gif

760 ms

c6.gif

c6.gif

772 ms

c7.gif

c7.gif

778 ms

c8.gif

c8.gif

855 ms

c9.gif

c9.gif

886 ms

c10.gif

c10.gif

939 ms

c11.gif

c11.gif

940 ms

c12.gif

c12.gif

951 ms

logo.gif

logo.gif

178 ms

login_button.gif

login_button.gif

320 ms

member_button.gif

member_button.gif

332 ms

topmenu.gif

topmenu.gif

332 ms

search.gif

search.gif

335 ms

list_title.gif

list_title.gif

356 ms

l_title_bottom.gif

l_title_bottom.gif

553 ms

tel_title.gif

tel_title.gif

637 ms

telicon.gif

telicon.gif

652 ms

trans.gif

trans.gif

665 ms

mailicon.gif

mailicon.gif

684 ms

sjk4649_blog.gif

sjk4649_blog.gif

686 ms

sjk4649_daibiki.gif

sjk4649_daibiki.gif

889 ms

sjk4649_qr.gif

sjk4649_qr.gif

971 ms

sjk4649_newimage1gif.gif

sjk4649_newimage1gif.gif

1010 ms

main_logo.jpg

main_logo.jpg

1764 ms

maintitle1.gif

maintitle1.gif

1011 ms

0030010000013.gif

0030010000013.gif

1224 ms

icon12.gif

icon12.gif

1222 ms

mk_main_p_line.gif

mk_main_p_line.gif

1281 ms

0020020000013.gif

0020020000013.gif

1469 ms

iconL.gif

iconL.gif

1366 ms

icony.gif

icony.gif

1556 ms

0020010000013.gif

0020010000013.gif

1784 ms

iconx.gif

iconx.gif

1615 ms

maintitle2.gif

maintitle2.gif

1695 ms

0040060000013.jpg

0040060000013.jpg

1805 ms

special_title.gif

special_title.gif

1891 ms

0120030000013.gif

0120030000013.gif

1948 ms

0010020000013.gif

0010020000013.gif

2031 ms

0060010000013.gif

0060010000013.gif

2262 ms

0060020000013.gif

0060020000013.gif

2283 ms

0010010000013.gif

0010010000013.gif

2160 ms

0120030000023.gif

0120030000023.gif

2198 ms

0040070000013.gif

0040070000013.gif

2326 ms

0040010000013.gif

0040010000013.gif

2390 ms

is_show_gmo_header.html

is_show_gmo_header.html

698 ms

aq_tag_aos.js

aq_tag_aos.js

141 ms

364 ms

EM34BYVZ46DUGEQNJE6A

EM34BYVZ46DUGEQNJE6A

143 ms

0070010000013.gif

0070010000013.gif

2300 ms

icon5.gif

icon5.gif

2219 ms

0090020000013.gif

0090020000013.gif

2452 ms

topbottom.gif

topbottom.gif

2294 ms

l_title_bg.gif

l_title_bg.gif

2309 ms

mk_main_underline.gif

mk_main_underline.gif

2352 ms

gmsync

gmsync

297 ms

segmentation.js

segmentation.js

55 ms

298 ms

cnt

cnt

351 ms

beacon.html

beacon.html

43 ms

pixel

pixel

19 ms

cs

cs

297 ms

Pug

Pug

21 ms

set

set

306 ms

tap.php

tap.php

6 ms

pixel

pixel

15 ms

sync

sync

15 ms

sync

sync

352 ms

sd

sd

26 ms

sync

sync

253 ms

mapuser

mapuser

149 ms

sync

sync

332 ms

SEO Factors

magepaipu.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Magepaipu.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 Magepaipu.com main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

magepaipu.com

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