Tools & Wizards About Us
ideacard.jp screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    90% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

ideacard.jp

アイデアカード公式サイト

Page Load Speed

2.6 sec in total

First Response

709 ms

Resources Loaded

1.8 sec

Page Rendered

157 ms

ideacard.jp screenshot

About Website

Click here to check amazing Ideacard content for Japan. Otherwise, check out these important facts you probably never knew about ideacard.jp

岡野弘文が発案したアイデアカードは、2万通りのアイデアやアイデアのヒントを得ることができる、無限の可能性を持ったカードです。

Visit ideacard.jp

Key Findings

We analyzed Ideacard.jp page load time and found that the first response time was 709 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

ideacard.jp performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

ideacard.jp

709 ms

newstyle.css

353 ms

ideacard_top3.jpg

536 ms

bijin_idea468x60.gif

552 ms

ideacard_bn480.jpg

890 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that all of those requests were addressed to Ideacard.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (890 ms) belongs to the original domain Ideacard.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.3 kB (21%)

Content Size

93.1 kB

After Optimization

73.9 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Ideacard.jp main page is 93.1 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 84.1 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 3.5 kB

  • Original 5.8 kB
  • After minification 5.6 kB
  • After compression 2.3 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 3.5 kB or 61% of the original size.

Image Optimization

-16%

Potential reduce by 13.3 kB

  • Original 84.1 kB
  • After minification 70.8 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, Ideacard needs image optimization as it can save up to 13.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-75%

Potential reduce by 2.4 kB

  • Original 3.2 kB
  • After minification 2.6 kB
  • After compression 784 B

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. Ideacard.jp needs all CSS files to be minified and compressed as it can save up to 2.4 kB or 75% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

  • Images
  • CSS

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ideacard. According to our analytics all requests are already optimized.

Network Requests Diagram

ideacard.jp

ideacard.jp

709 ms

newstyle.css

newstyle.css

353 ms

ideacard_top3.jpg

ideacard_top3.jpg

536 ms

bijin_idea468x60.gif

bijin_idea468x60.gif

552 ms

ideacard_bn480.jpg

ideacard_bn480.jpg

890 ms

Accessibility Review

ideacard.jp accessibility score

68

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.

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

Best Practices

ideacard.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

ideacard.jp SEO score

69

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ideacard.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 Ideacard.jp main page’s claimed encoding is shift_jis. 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

ideacard.jp

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