Access a-proj.jp. 有名建築家と建てる住まい｜Ａプロジェクト|ミサワホーム

a-proj.jp screenshot

69

Performance

Renders faster than
80% of other websites
59

Accessibility

Visual factors better than
that of 26% of websites
75

Best Practices

More advanced features
available than in
35% of websites
58

SEO

Google-friendlier than
21% of websites

First Response

1.1 sec

Resources Loaded

9.4 sec

Page Rendered

224 ms

a-proj.jp screenshot

About Website

Welcome to a-proj.jp homepage info - get ready to check A Proj best content right away, or after learning these important things about a-proj.jp

有名建築家と建てる住まいなら、ミサワホームの建築プロデュース『Ａプロジェクト』。建築家と家を建てる人をサポートいたします。

Visit a-proj.jp

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

75/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

a-proj.jp

1146 ms

common.css

529 ms

top.css

357 ms

pop.css

379 ms

popup.js

782 ms

Our browser made a total of 213 requests to load all elements on the main page. We found that 94% of them (201 requests) were addressed to the original A-proj.jp, 1% (3 requests) were made to Platform.twitter.com and 1% (2 requests) were made to Bmmetrix.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain A-proj.jp.

Content Size

2.3 MB

After Optimization

2.1 MB

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

HTML Optimization

-83%

Potential reduce by 35.9 kB

Original 43.1 kB
After minification 36.9 kB
After compression 7.3 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 6.2 kB, which is 14% 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 35.9 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 68.5 kB

Original 2.2 MB
After minification 2.1 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. A Proj images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 13.5 kB

Original 20.1 kB
After minification 19.7 kB
After compression 6.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 13.5 kB or 67% of the original size.

CSS Optimization

-78%

Potential reduce by 6.2 kB

Original 8.0 kB
After minification 6.6 kB
After compression 1.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. A-proj.jp needs all CSS files to be minified and compressed as it can save up to 6.2 kB or 78% of the original size.

Requests Now

201

After Optimization

177

The browser has sent 201 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A Proj. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts 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 semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A-proj.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 A-proj.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

a-proj.jp

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