Report Summary

  • 2

    Performance

    Renders faster than
    19% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

proud-web.jp

プラウド-PROUD-野村不動産の新築分譲マンション、新築一戸建て

Page Load Speed

18.1 sec in total

First Response

13 ms

Resources Loaded

17.3 sec

Page Rendered

840 ms

proud-web.jp screenshot

About Website

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

【公式】新築分譲マンション、新築一戸建てをお探しなら野村不動産【プラウド-PROUD‐】安心して長く暮らせる住まいをプラウドで見つけてください。首都圏を始め、関西、名古屋・近郊、仙台、北関東・福島、中部で物件を展開中。『世界一の時間へ。』

Visit proud-web.jp

Key Findings

We analyzed Proud-web.jp page load time and found that the first response time was 13 ms and then it took 18.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

proud-web.jp performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value58.0 s

0/100

25%

SI (Speed Index)

Value30.9 s

0/100

10%

TBT (Total Blocking Time)

Value8,290 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.566

12/100

15%

TTI (Time to Interactive)

Value119.9 s

0/100

10%

Network Requests Diagram

proud-web.jp

13 ms

proud-web.jp

179 ms

www.proud-web.jp

223 ms

base.css

1026 ms

module.css

1213 ms

Our browser made a total of 333 requests to load all elements on the main page. We found that 73% of them (244 requests) were addressed to the original Proud-web.jp, 4% (12 requests) were made to Googletagmanager.com and 2% (5 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Proud-web.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (14%)

Content Size

18.2 MB

After Optimization

15.7 MB

In fact, the total size of Proud-web.jp main page is 18.2 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. Only a small number of websites need less resources to load. Images take 15.9 MB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 339.4 kB

  • Original 366.2 kB
  • After minification 251.3 kB
  • After compression 26.8 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 114.9 kB, which is 31% 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 339.4 kB or 93% of the original size.

Image Optimization

-6%

Potential reduce by 1.0 MB

  • Original 15.9 MB
  • After minification 14.9 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. PROUD Web images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 627.3 kB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 719.3 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 627.3 kB or 47% of the original size.

CSS Optimization

-89%

Potential reduce by 531.2 kB

  • Original 598.4 kB
  • After minification 469.8 kB
  • After compression 67.2 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. Proud-web.jp needs all CSS files to be minified and compressed as it can save up to 531.2 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 93 (35%)

Requests Now

269

After Optimization

176

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

Accessibility Review

proud-web.jp accessibility score

72

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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.

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

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

proud-web.jp best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

proud-web.jp SEO score

99

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Proud-web.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Proud-web.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 data is detected on the main page of PROUD Web. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: