Report Summary

  • 17

    Performance

    Renders faster than
    36% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    34% of websites

  • 84

    SEO

    Google-friendlier than
    60% of websites

topick.jp

TOPICK - インスピレーションを刺激するわくわくネタをお届け

Page Load Speed

10 sec in total

First Response

1.6 sec

Resources Loaded

7.7 sec

Page Rendered

631 ms

topick.jp screenshot

About Website

Visit topick.jp now to see the best up-to-date TOPICK content for Japan and also check out these interesting facts you probably never knew about topick.jp

TOPICKは気になる情報をピックアップしてお伝えするブログです面白いガジェットやツール、アート、グラフィックその他ジャンル問わずワクワクするようなネタを紹介。TOPICKのサイト名は「TOPIC」と「PICK UP」を組み合わせた造語です。

Visit topick.jp

Key Findings

We analyzed Topick.jp page load time and found that the first response time was 1.6 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

topick.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value1,860 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.114

86/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

topick.jp

1643 ms

skeleton.css

513 ms

base.css

519 ms

flexslider.css

366 ms

font-awesome.css

723 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 54% of them (71 requests) were addressed to the original Topick.jp, 6% (8 requests) were made to Pbs.twimg.com and 5% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Topick.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 986.4 kB (35%)

Content Size

2.9 MB

After Optimization

1.9 MB

In fact, the total size of Topick.jp main page is 2.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 49.5 kB

  • Original 64.3 kB
  • After minification 62.3 kB
  • After compression 14.8 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 49.5 kB or 77% of the original size.

Image Optimization

-9%

Potential reduce by 156.7 kB

  • Original 1.7 MB
  • After minification 1.5 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. TOPICK images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 626.1 kB

  • Original 942.9 kB
  • After minification 934.6 kB
  • After compression 316.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 626.1 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 154.1 kB

  • Original 180.4 kB
  • After minification 136.1 kB
  • After compression 26.2 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. Topick.jp needs all CSS files to be minified and compressed as it can save up to 154.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (51%)

Requests Now

129

After Optimization

63

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

Accessibility Review

topick.jp accessibility score

57

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

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

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

topick.jp best practices score

67

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

topick.jp SEO score

84

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 Topick.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 Topick.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 TOPICK. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: