Access oldtokyo.com. Old Tokyo | Vintage Japanese postcards and ephemera.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.215

58/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

www.oldtokyo.com

1707 ms

wp-emoji-release.min.js

16 ms

style.css

20 ms

css

43 ms

css

81 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 71% of them (51 requests) were addressed to the original Oldtokyo.com, 14% (10 requests) were made to Fonts.googleapis.com and 10% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Oldtokyo.com.

Content Size

2.7 MB

After Optimization

2.1 MB

In fact, the total size of Oldtokyo.com main page is 2.7 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 144.7 kB

Original 168.8 kB
After minification 163.0 kB
After compression 24.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. 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 144.7 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 128.8 kB

Original 2.1 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. Old Tokyo images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 177.6 kB

Original 271.1 kB
After minification 241.0 kB
After compression 93.5 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 177.6 kB or 66% of the original size.

CSS Optimization

-88%

Potential reduce by 159.8 kB

Original 180.6 kB
After minification 140.9 kB
After compression 20.9 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. Oldtokyo.com needs all CSS files to be minified and compressed as it can save up to 159.8 kB or 88% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

ARIA IDs are not unique

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document doesn't use 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 Oldtokyo.com 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 Oldtokyo.com 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

oldtokyo.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Old Tokyo | Vintage Japanese postcards and ephemera.

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

www.oldtokyo.com

wp-emoji-release.min.js

style.css

css

css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

www.oldtokyo.com

wp-emoji-release.min.js

style.css

css

css

css

prettyPhoto.css

wds_frontend.css

wds_effects.css

font-awesome.css

jquery.js

jquery-migrate.min.js

jquery.prettyPhoto.js

front.js

jquery.mobile.js

jquery.featureCarouselslider.js

no-right-click-images.js

style.css

toggle.js

jquery.infinitescroll.js

wp-embed.min.js

scripts.js

style.css

css

css

css

css

css

css

css

analytics.js

canvas-fabric.jpg

feed2.png

oldtokyo-banner-500.png

ajax_loader.png

imperial-hotel940.jpg

scan0017-360x360.jpg

scan0004-1-360x360.jpg

scan0008-360x360.jpg

scan0010-1-360x360.jpg

scan0004-360x360.jpg

ginza-tokyu-kabuki-300-360x360.jpg

scan0002-360x360.jpg