Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

pitatoku.com

徳島の賃貸マンション・賃貸物件情報はピタットハウス徳島店へ

Page Load Speed

10.1 sec in total

First Response

577 ms

Resources Loaded

8.7 sec

Page Rendered

794 ms

pitatoku.com screenshot

About Website

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

徳島の賃貸マンション情報は、ピタットハウス徳島店へ。徳島文理大学生向けの賃貸物件をはじめ、徳島市・小松島市など幅広い徳島エリアの賃貸情報を取り扱っています。徳島市内の新築・築浅・戸建賃貸物件もお任せ下さい。当店は、徳島での移動に便利な国道11号線沿いに有ります。ご来店・賃貸のお部屋見学の移動にも、大変便利です。

Visit pitatoku.com

Key Findings

We analyzed Pitatoku.com page load time and found that the first response time was 577 ms and then it took 9.5 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

pitatoku.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value21.4 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value1,930 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.557

13/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

pitatoku.com

577 ms

www.pitatoku.com

1526 ms

ga.js

46 ms

all.js

9 ms

140 ms

Our browser made a total of 196 requests to load all elements on the main page. We found that 93% of them (183 requests) were addressed to the original Pitatoku.com, 2% (3 requests) were made to Platform.twitter.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Pitatoku.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 425.7 kB (11%)

Content Size

3.9 MB

After Optimization

3.4 MB

In fact, the total size of Pitatoku.com main page is 3.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. 55% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 91.3 kB

  • Original 108.2 kB
  • After minification 104.0 kB
  • After compression 17.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. 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 91.3 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 140.4 kB

  • Original 3.5 MB
  • After minification 3.3 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. Pitatoku images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 118.1 kB

  • Original 178.6 kB
  • After minification 150.6 kB
  • After compression 60.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 118.1 kB or 66% of the original size.

CSS Optimization

-88%

Potential reduce by 76.0 kB

  • Original 86.6 kB
  • After minification 53.7 kB
  • After compression 10.6 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. Pitatoku.com needs all CSS files to be minified and compressed as it can save up to 76.0 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (26%)

Requests Now

194

After Optimization

144

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

Accessibility Review

pitatoku.com accessibility score

74

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

pitatoku.com 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

High

Page has valid source maps

SEO Factors

pitatoku.com SEO score

85

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 Pitatoku.com 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 Pitatoku.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

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