Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

q-pot.jp

Q-pot. OFFICIAL HOMEPAGE

Page Load Speed

3.4 sec in total

First Response

298 ms

Resources Loaded

2.8 sec

Page Rendered

285 ms

About Website

Click here to check amazing Q Pot content for Japan. Otherwise, check out these important facts you probably never knew about q-pot.jp

   

Visit q-pot.jp

Key Findings

We analyzed Q-pot.jp page load time and found that the first response time was 298 ms and then it took 3.1 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

q-pot.jp performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value18.6 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value6,020 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.076

2/100

15%

TTI (Time to Interactive)

Value28.5 s

0/100

10%

Network Requests Diagram

q-pot.jp

298 ms

gtm.js

69 ms

style_20180215.css

56 ms

jquery.bxslider.min.css

126 ms

font-awesome.min.css

46 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 44% of them (41 requests) were addressed to the original Q-pot.jp, 12% (11 requests) were made to Platform.twitter.com and 6% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Syndication.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 452.0 kB (17%)

Content Size

2.7 MB

After Optimization

2.2 MB

In fact, the total size of Q-pot.jp main page is 2.7 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 33.2 kB

  • Original 44.3 kB
  • After minification 37.2 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 7.1 kB, which is 16% 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 33.2 kB or 75% of the original size.

Image Optimization

-11%

Potential reduce by 240.7 kB

  • Original 2.3 MB
  • After minification 2.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. Obviously, Q Pot needs image optimization as it can save up to 240.7 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

-49%

Potential reduce by 169.3 kB

  • Original 347.2 kB
  • After minification 335.9 kB
  • After compression 177.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 169.3 kB or 49% of the original size.

CSS Optimization

-50%

Potential reduce by 8.8 kB

  • Original 17.6 kB
  • After minification 17.6 kB
  • After compression 8.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. Q-pot.jp needs all CSS files to be minified and compressed as it can save up to 8.8 kB or 50% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (62%)

Requests Now

89

After Optimization

34

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

Accessibility Review

q-pot.jp accessibility score

77

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

q-pot.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

q-pot.jp SEO score

72

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

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/).

Impact

Issue

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 Q-pot.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 Q-pot.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

Open Graph data is detected on the main page of Q Pot. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: