Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

tamaliver.jp

多摩地区の地域ブログサービス たまりば|八王子,立川,吉祥寺,調布,三鷹などの地域ポータルサイト

Page Load Speed

16.7 sec in total

First Response

1.3 sec

Resources Loaded

11.1 sec

Page Rendered

4.3 sec

tamaliver.jp screenshot

About Website

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

八王子、立川、武蔵野、三鷹、調布、日野、国分寺、小平、西東京など、多摩地区のブログサービス「たまりば」。会員登録、ブログ開設は無料。Twitter、Facebookとの相性も抜群。多摩地区・多摩地域のお店・会社の宣伝、集客にもご活用下さい。

Visit tamaliver.jp

Key Findings

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

Performance Metrics

tamaliver.jp performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value18.0 s

0/100

25%

SI (Speed Index)

Value25.9 s

0/100

10%

TBT (Total Blocking Time)

Value52,050 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.214

58/100

15%

TTI (Time to Interactive)

Value68.8 s

0/100

10%

Network Requests Diagram

tamaliver.jp

1337 ms

renewal.css

665 ms

jquery.min.js

32 ms

rss_reader.php

903 ms

rss_reader.php

507 ms

Our browser made a total of 237 requests to load all elements on the main page. We found that 42% of them (100 requests) were addressed to the original Tamaliver.jp, 26% (61 requests) were made to Img01.tamaliver.jp and 4% (9 requests) were made to Aka-uliza2-vod.uliza.jp. The less responsive or slowest element that took the longest time to load (5.8 sec) relates to the external source Img01.tamaliver.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 335.2 kB (14%)

Content Size

2.5 MB

After Optimization

2.1 MB

In fact, the total size of Tamaliver.jp main page is 2.5 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 98.1 kB

  • Original 124.5 kB
  • After minification 114.0 kB
  • After compression 26.4 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 98.1 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 122.3 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. Tamaliver images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 67.7 kB

  • Original 172.3 kB
  • After minification 172.1 kB
  • After compression 104.6 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 67.7 kB or 39% of the original size.

CSS Optimization

-91%

Potential reduce by 47.1 kB

  • Original 51.9 kB
  • After minification 38.5 kB
  • After compression 4.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. Tamaliver.jp needs all CSS files to be minified and compressed as it can save up to 47.1 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 100 (43%)

Requests Now

230

After Optimization

130

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

Accessibility Review

tamaliver.jp accessibility score

65

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.

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

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

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

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

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

tamaliver.jp best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tamaliver.jp SEO score

83

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 Tamaliver.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 Tamaliver.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 Tamaliver. 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: