Access ampleg.com. 株式会社アンプルグリッド | 愛媛県松山市からウェブサービスを提供

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.619

10/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

ampleg.com

926 ms

style.css

923 ms

media.css

746 ms

revolution.css

750 ms

media-slideshow.css

363 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 81% of them (42 requests) were addressed to the original Ampleg.com, 12% (6 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Ampleg.com.

Content Size

715.7 kB

After Optimization

217.7 kB

In fact, the total size of Ampleg.com main page is 715.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. 30% of websites need less resources to load. Javascripts take 342.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 16.3 kB

Original 21.9 kB
After minification 16.1 kB
After compression 5.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 5.8 kB, which is 27% 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 16.3 kB or 75% of the original size.

Image Optimization

-14%

Potential reduce by 8.8 kB

Original 60.7 kB
After minification 51.9 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, Ampleg needs image optimization as it can save up to 8.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 226.6 kB

Original 342.2 kB
After minification 325.4 kB
After compression 115.6 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 226.6 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 246.3 kB

Original 290.9 kB
After minification 260.0 kB
After compression 44.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. Ampleg.com needs all CSS files to be minified and compressed as it can save up to 246.3 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

robots.txt is not valid

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Ampleg.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 Ampleg.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

ampleg.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

株式会社アンプルグリッド | 愛媛県松山市からウェブサービスを提供

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

ampleg.com

style.css

media.css

revolution.css

media-slideshow.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

ampleg.com

style.css

media.css

revolution.css

media-slideshow.css

noscript.css

css

css

css

jquery.min.js

jquery.easing-1.3.min.js

modernizr.js

superfish.js

jquery.carouFredSel-6.2.1-packed.js

jquery.themepunch.plugins.min.js

jquery.themepunch.revolution.min.js

mediaelement-and-player.min.js

jquery.fancybox.js

jquery.fancybox-media.js

jquery.donutchart.js

jflickrfeed.min.js

jquery.twitter.js

accordion-functions.js

theme-functions.js

jquery.retina.js

base.css

grid.css

icons.css

audio.css

loading_slideshow.gif

logo.png

active_menu_green.gif

icon-arrow.png

icon-compas.png

icon-money.png

icon-help.png

active_menu_grey.gif

icon-config.png

icon-note.png

icon-ribbon.png

icon-portfolio.png

icon-truck.png

icon-bag.png