Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

iid.backlog.jp

Login - Nulab Account

Page Load Speed

2 sec in total

First Response

309 ms

Resources Loaded

1.6 sec

Page Rendered

91 ms

iid.backlog.jp screenshot

About Website

Welcome to iid.backlog.jp homepage info - get ready to check Iid Backlog best content for Japan right away, or after learning these important things about iid.backlog.jp

A single sign-on service connecting you to all Nulab apps with one password.

Visit iid.backlog.jp

Key Findings

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

Performance Metrics

iid.backlog.jp performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value3.0 s

93/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.132

81/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

iid.backlog.jp

309 ms

LoginDisplay.action

211 ms

Login.css

49 ms

theme.css

54 ms

common-libs.js

66 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 12% of them (4 requests) were addressed to the original Iid.backlog.jp, 88% (29 requests) were made to Assets.backlog.jp. The less responsive or slowest element that took the longest time to load (309 ms) belongs to the original domain Iid.backlog.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.6 kB (29%)

Content Size

29.9 kB

After Optimization

21.4 kB

In fact, the total size of Iid.backlog.jp main page is 29.9 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. 25% of websites need less resources to load. Images take 20.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 7.1 kB

  • Original 9.5 kB
  • After minification 7.8 kB
  • After compression 2.5 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 1.7 kB, which is 18% 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 7.1 kB or 74% of the original size.

Image Optimization

-7%

Potential reduce by 1.5 kB

  • Original 20.4 kB
  • After minification 18.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. Iid Backlog images are well optimized though.

Requests Breakdown

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

Requests Now

31

After Optimization

14

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

Accessibility Review

iid.backlog.jp accessibility score

88

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.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

iid.backlog.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

iid.backlog.jp SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iid.backlog.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Iid.backlog.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 description is not detected on the main page of Iid Backlog. 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: