Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

code4.nagoya

Code for Nagoya

Page Load Speed

3.3 sec in total

First Response

202 ms

Resources Loaded

1.2 sec

Page Rendered

2 sec

code4.nagoya screenshot

About Website

Visit code4.nagoya now to see the best up-to-date Code 4 content and also check out these interesting facts you probably never knew about code4.nagoya

テクノロジーで街を楽しく!

Visit code4.nagoya

Key Findings

We analyzed Code4.nagoya page load time and found that the first response time was 202 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

code4.nagoya performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

84/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value440 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value6.3 s

60/100

10%

Network Requests Diagram

code4.nagoya

202 ms

code4.nagoya

312 ms

pre_tumblelog.js

63 ms

index.build.css

72 ms

main-min.css

60 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Code4.nagoya, 40% (17 requests) were made to Assets.tumblr.com and 31% (13 requests) were made to 64.media.tumblr.com. The less responsive or slowest element that took the longest time to load (544 ms) relates to the external source 64.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 227.5 kB (57%)

Content Size

399.6 kB

After Optimization

172.2 kB

In fact, the total size of Code4.nagoya main page is 399.6 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. 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. HTML takes 274.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 227.1 kB

  • Original 274.1 kB
  • After minification 224.4 kB
  • After compression 47.0 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 49.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 227.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 104.0 kB
  • After minification 104.0 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. Code 4 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 6 B

  • Original 3.4 kB
  • After minification 3.4 kB
  • After compression 3.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 393 B

  • Original 18.2 kB
  • After minification 18.2 kB
  • After compression 17.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. Code4.nagoya has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (24%)

Requests Now

34

After Optimization

26

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

Accessibility Review

code4.nagoya accessibility score

61

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

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

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

code4.nagoya best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

code4.nagoya SEO score

90

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

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Code4.nagoya can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Code4.nagoya 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 Code 4. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: