Tools & Wizards About Us
neat-kk.jp screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

neat-kk.jp

株式会社ニート｜埼玉で家つくり｜埼玉でＳＥ構法|さいたまの家｜リフォーム｜耐震補強工事｜新築改修工事｜一級建築士｜木造

Page Load Speed

6.7 sec in total

First Response

697 ms

Resources Loaded

5.6 sec

Page Rendered

387 ms

neat-kk.jp screenshot

About Website

Welcome to neat-kk.jp homepage info - get ready to check Neat Kk best content right away, or after learning these important things about neat-kk.jp

埼玉県さいたま市の株式会社ニートでは、家造りの基本（空間・光線・風・動線）を重要な課題として家造りに社員一同取り組んでいます。お客様のご要望・ご意見を住みよい形にして家族の形態が変わった場合でも対応できる、構造を問わない自由設計の家造りをしています。注文住宅、狭小住宅、リフォーム、耐震診断のご用命の際には、どうぞお気軽にご連絡ください。

Visit neat-kk.jp

Key Findings

We analyzed Neat-kk.jp page load time and found that the first response time was 697 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

neat-kk.jp performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value19.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value1.149

1/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

neat-kk.jp

697 ms

reset.css

340 ms

pc.css

506 ms

font-awesome.css

342 ms

jquery.fancybox.min.css

346 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 88% of them (83 requests) were addressed to the original Neat-kk.jp, 4% (4 requests) were made to Maps.googleapis.com and 2% (2 requests) were made to Webfont.fontplus.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Neat-kk.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 104.1 kB (3%)

Content Size

3.1 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 65.6 kB

  • Original 84.7 kB
  • After minification 83.7 kB
  • After compression 19.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 65.6 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 6.4 kB

  • Original 2.6 MB
  • After minification 2.6 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. Neat Kk images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 19.3 kB

  • Original 303.7 kB
  • After minification 303.7 kB
  • After compression 284.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. This website has mostly compressed JavaScripts.

CSS Optimization

-20%

Potential reduce by 12.8 kB

  • Original 63.8 kB
  • After minification 63.8 kB
  • After compression 51.0 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. Neat-kk.jp needs all CSS files to be minified and compressed as it can save up to 12.8 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (53%)

Requests Now

92

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

neat-kk.jp

neat-kk.jp

697 ms

reset.css

reset.css

340 ms

pc.css

pc.css

506 ms

font-awesome.css

font-awesome.css

342 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

346 ms

photoswipe.css

photoswipe.css

345 ms

default-skin.css

default-skin.css

346 ms

froala_editor.pkgd.min.css

froala_editor.pkgd.min.css

513 ms

custom.css

custom.css

519 ms

design.css

design.css

526 ms

page.css

page.css

525 ms

jquery-3.5.1.js

jquery-3.5.1.js

1192 ms

jquery-migrate-1.4.1.js

jquery-migrate-1.4.1.js

675 ms

resize_img.js

resize_img.js

684 ms

jquery.easing.min.js

jquery.easing.min.js

686 ms

jquery.cookie.min.js

jquery.cookie.min.js

686 ms

ua_log.js

ua_log.js

687 ms

msg.js

msg.js

846 ms

slider-pro.min.css

slider-pro.min.css

855 ms

pc.css

pc.css

863 ms

jquery.dbpas.carousel.css

jquery.dbpas.carousel.css

870 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

857 ms

photoswipe.min.js

photoswipe.min.js

1013 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

1025 ms

photoswipe-set-customize.min.js

photoswipe-set-customize.min.js

1028 ms

jquery.sliderPro.min.js

jquery.sliderPro.min.js

2325 ms

imgCycle.min.js

imgCycle.min.js

1039 ms

jquery.ba-throttle-debounce.min.js

jquery.ba-throttle-debounce.min.js

1183 ms

jquery.cycle.all.js

jquery.cycle.all.js

2159 ms

jquery.dbpas.carousel.js

jquery.dbpas.carousel.js

2164 ms

map_common.min.js

map_common.min.js

2164 ms

counterFix.js

counterFix.js

2165 ms

marquee.min.js

marquee.min.js

2165 ms

onload.min.js

onload.min.js

2165 ms

scrollmenu.js

scrollmenu.js

2165 ms

analysis.js

analysis.js

2165 ms

fontplus.js

fontplus.js

585 ms

analytics.js

analytics.js

73 ms

201712120928572074.png

201712120928572074.png

190 ms

201612291134406279.png

201612291134406279.png

354 ms

201612291135533987.png

201612291135533987.png

354 ms

201612291136385163.png

201612291136385163.png

684 ms

201612291147377279.png

201612291147377279.png

188 ms

201612291150116463.png

201612291150116463.png

187 ms

201302251938473943.jpg

201302251938473943.jpg

510 ms

201302251937379650.jpg

201302251937379650.jpg

856 ms

201305221439366469.JPG

201305221439366469.JPG

1534 ms

201408281131025672.JPG

201408281131025672.JPG

1192 ms

201607061339595430.JPG

201607061339595430.JPG

1025 ms

201607061326529116.jpg

201607061326529116.jpg

1351 ms

201607061330335643.jpg

201607061330335643.jpg

1363 ms

201607201116195788.jpg

201607201116195788.jpg

1039 ms

201607201110508639.JPG

201607201110508639.JPG

1206 ms

201607201105485084.JPG

201607201105485084.JPG

1391 ms

201706061154204392.jpg

201706061154204392.jpg

1535 ms

201706061155115406.jpg

201706061155115406.jpg

1556 ms

20170119114924113.jpg

20170119114924113.jpg

1521 ms

qr.png

qr.png

1542 ms

header_bg.png

header_bg.png

1565 ms

header.png

header.png

1685 ms

catch_bg.jpg

catch_bg.jpg

1653 ms

201612291105581487.jpg

201612291105581487.jpg

2001 ms

201706201102408280.jpg

201706201102408280.jpg

1848 ms

201706201106291320.JPG

201706201106291320.JPG

2188 ms

201706201108386716.JPG

201706201108386716.JPG

2195 ms

201706201115082101.JPG

201706201115082101.JPG

2151 ms

b_title.png

b_title.png

1827 ms

201302251937379650.jpg

201302251937379650.jpg

2002 ms

201305221439366469.JPG

201305221439366469.JPG

2021 ms

201408281131025672.JPG

201408281131025672.JPG

2177 ms

201607061339595430.JPG

201607061339595430.JPG

2185 ms

201607061326529116.jpg

201607061326529116.jpg

2200 ms

201607061330335643.jpg

201607061330335643.jpg

2322 ms

menu_top.png

menu_top.png

2360 ms

collect

collect

37 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2236 ms

menu_b.png

menu_b.png

2241 ms

menu_bottom.png

menu_bottom.png

2247 ms

js

js

102 ms

mkfont

mkfont

391 ms

3d4c80e6

3d4c80e6

316 ms

bottom_bg.jpg

bottom_bg.jpg

2090 ms

place

place

334 ms

f_menu_bg.jpg

f_menu_bg.jpg

2210 ms

footer_bg.jpg

footer_bg.jpg

2088 ms

page_top.png

page_top.png

1924 ms

js

js

29 ms

search.js

search.js

5 ms

geometry.js

geometry.js

9 ms

main.js

main.js

12 ms

openhand.cur

openhand.cur

1743 ms

catch_pleft.png

catch_pleft.png

1587 ms

catch_pright.png

catch_pright.png

1583 ms

catch_frame.png

catch_frame.png

1549 ms

Accessibility Review

neat-kk.jp accessibility score

89

Accessibility Issues

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

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

neat-kk.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

neat-kk.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

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 Neat-kk.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 Neat-kk.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

neat-kk.jp

Open Graph data is detected on the main page of Neat Kk. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: