Tools & Wizards About Us
q-pot.jp screenshot

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

q-pot.jp screenshot

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 547.2 kB (20%)

Content Size

2.8 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Q-pot.jp main page is 2.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. 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

-60%

Potential reduce by 264.5 kB

  • Original 442.4 kB
  • After minification 431.1 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 264.5 kB or 60% 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

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

q-pot.jp

q-pot.jp

298 ms

gtm.js

gtm.js

69 ms

style_20180215.css

style_20180215.css

56 ms

jquery.bxslider.min.css

jquery.bxslider.min.css

126 ms

font-awesome.min.css

font-awesome.min.css

46 ms

normalize.min.css

normalize.min.css

125 ms

drawer.min.css

drawer.min.css

122 ms

jquery.min.js

jquery.min.js

38 ms

rss.js

rss.js

141 ms

jsapi

jsapi

37 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

184 ms

jquery.feeds.min.js

jquery.feeds.min.js

151 ms

iscroll.min.js

iscroll.min.js

221 ms

dropdown.min.js

dropdown.min.js

185 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

324 ms

drawer.min.js

drawer.min.js

186 ms

snowfall.jquery.js

snowfall.jquery.js

229 ms

loader.min.js

loader.min.js

46 ms

loader.js

loader.js

20 ms

analytics.js

analytics.js

50 ms

uwt.js

uwt.js

37 ms

adsct

adsct

250 ms

adsct

adsct

252 ms

linkid.js

linkid.js

13 ms

collect

collect

21 ms

collect

collect

94 ms

js

js

118 ms

ja.png

ja.png

479 ms

widgets.js

widgets.js

179 ms

ga.js

ga.js

66 ms

q-pot-to-page.js

q-pot-to-page.js

475 ms

rss.php

rss.php

569 ms

17841402617934865

17841402617934865

939 ms

sp_shop_logo.png

sp_shop_logo.png

154 ms

cafe_sp_logo.png

cafe_sp_logo.png

153 ms

h_menu_icon.png

h_menu_icon.png

153 ms

header_logo.png

header_logo.png

152 ms

twi_logo.png

twi_logo.png

153 ms

fb_logo.png

fb_logo.png

229 ms

insta_logo.png

insta_logo.png

228 ms

Main_Visual01.jpg

Main_Visual01.jpg

501 ms

Main_Visual02.jpg

Main_Visual02.jpg

500 ms

Main_Visual03.jpg

Main_Visual03.jpg

659 ms

Main_Visual04.jpg

Main_Visual04.jpg

565 ms

Main_Visual05.jpg

Main_Visual05.jpg

510 ms

3_recruit.jpg

3_recruit.jpg

606 ms

1_cafe.jpg

1_cafe.jpg

565 ms

online_sp.png

online_sp.png

565 ms

online.png

online.png

607 ms

Sub_Visual02.jpg

Sub_Visual02.jpg

609 ms

about.png

about.png

611 ms

collection.png

collection.png

665 ms

twi_acc.png

twi_acc.png

660 ms

insta_acc.png

insta_acc.png

661 ms

twi_logo_sp.png

twi_logo_sp.png

663 ms

fb_logo_sp.png

fb_logo_sp.png

666 ms

insta_logo_sp.png

insta_logo_sp.png

713 ms

bx_loader.gif

bx_loader.gif

714 ms

arrow_left.png

arrow_left.png

716 ms

arrow_right.png

arrow_right.png

717 ms

ga-audiences

ga-audiences

142 ms

__utm.gif

__utm.gif

98 ms

__utm.gif

__utm.gif

92 ms

fbevents.js

fbevents.js

123 ms

optimize.js

optimize.js

166 ms

js

js

192 ms

collect

collect

100 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

324 ms

426203241157192

426203241157192

230 ms

ga-audiences

ga-audiences

194 ms

banner_q_pot_1516x90_en.jpg

banner_q_pot_1516x90_en.jpg

10 ms

settings

settings

69 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

20 ms

QpotJAPAN

QpotJAPAN

1542 ms

friend

friend

335 ms

friend

friend

280 ms

441495479_1473045963639560_5920755902283700658_n.jpg

441495479_1473045963639560_5920755902283700658_n.jpg

21 ms

441201481_1106662303893917_5524199359517638179_n.jpg

441201481_1106662303893917_5524199359517638179_n.jpg

24 ms

441494790_971964650975598_3569601597531788529_n.jpg

441494790_971964650975598_3569601597531788529_n.jpg

23 ms

441465366_1452183245388121_3223876372299594333_n.jpg

441465366_1452183245388121_3223876372299594333_n.jpg

27 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

21 ms

widget.1.23.1.7.css

widget.1.23.1.7.css

206 ms

button.1.23.1.7.js

button.1.23.1.7.js

199 ms

sentry.1.23.1.7.js

sentry.1.23.1.7.js

201 ms

torimochi.js

torimochi.js

14 ms

line_v3@3x.png

line_v3@3x.png

3 ms

polyfills-3b821eda8863adcc4a4b.js

polyfills-3b821eda8863adcc4a4b.js

19 ms

runtime-a697c5a1ae32bd7e4d42.js

runtime-a697c5a1ae32bd7e4d42.js

38 ms

modules.20f98d7498a59035a762.js

modules.20f98d7498a59035a762.js

80 ms

main-fd9ef5eb169057cda26d.js

main-fd9ef5eb169057cda26d.js

74 ms

_app-88bf420a57d49e33be53.js

_app-88bf420a57d49e33be53.js

81 ms

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

81 ms

_buildManifest.js

_buildManifest.js

81 ms

_ssgManifest.js

_ssgManifest.js

83 ms

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

q-pot.jp

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: