Tools & Wizards About Us
airnavi.jp screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

airnavi.jp

エアナビ｜東京の個人事業主を中心にエアコン取付

Page Load Speed

3.9 sec in total

First Response

405 ms

Resources Loaded

3.3 sec

Page Rendered

187 ms

airnavi.jp screenshot

About Website

Click here to check amazing Airnavi content. Otherwise, check out these important facts you probably never knew about airnavi.jp

「より快適で清潔な空間で生活を送りたい」ほとんどの方がこう思われていると思います。エアナビでは、そんな願いを叶えるお手伝いを行っております。空間づくりのお手伝いとして業務用エアコンの設置を行い、今以上の快適さや清潔さをご提案いたします。

Visit airnavi.jp

Key Findings

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

Performance Metrics

airnavi.jp performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

airnavi.jp

405 ms

www.airnavi.jp

330 ms

import.css

149 ms

air.css

294 ms

print.css

298 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 82% of them (45 requests) were addressed to the original Airnavi.jp, 4% (2 requests) were made to Seal.globalsign.com and 4% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Airnavi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 785.8 kB (69%)

Content Size

1.1 MB

After Optimization

357.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Airnavi.jp main page is 1.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. 35% of websites need less resources to load. Javascripts take 833.6 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 65.4 kB

  • Original 75.7 kB
  • After minification 68.5 kB
  • After compression 10.2 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.4 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 5.9 kB

  • Original 174.2 kB
  • After minification 168.4 kB

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. Airnavi images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 667.1 kB

  • Original 833.6 kB
  • After minification 775.5 kB
  • After compression 166.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 667.1 kB or 80% of the original size.

CSS Optimization

-80%

Potential reduce by 47.4 kB

  • Original 59.5 kB
  • After minification 52.6 kB
  • After compression 12.1 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. Airnavi.jp needs all CSS files to be minified and compressed as it can save up to 47.4 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

51

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

airnavi.jp

airnavi.jp

405 ms

www.airnavi.jp

www.airnavi.jp

330 ms

import.css

import.css

149 ms

air.css

air.css

294 ms

print.css

print.css

298 ms

smart.js

smart.js

296 ms

search.css

search.css

299 ms

othercity.css

othercity.css

303 ms

jquery-ui-1.9.2.custom.min.css

jquery-ui-1.9.2.custom.min.css

305 ms

jquery.min.js

jquery.min.js

30 ms

jquery-ui.min.js

jquery-ui.min.js

10 ms

jquery-ui-1.9.2.custom.min.js

jquery-ui-1.9.2.custom.min.js

441 ms

jquery.ui.datepicker-ja.js

jquery.ui.datepicker-ja.js

439 ms

calendar-holidays.js

calendar-holidays.js

441 ms

jquery.blockUI.js

jquery.blockUI.js

446 ms

spin.js

spin.js

452 ms

sender.js

sender.js

454 ms

all_master.js

all_master.js

1080 ms

setupmaster.js

setupmaster.js

589 ms

air_toppage.js

air_toppage.js

587 ms

information.js

information.js

595 ms

air_common.js

air_common.js

604 ms

gs_image_100-50_ja.js

gs_image_100-50_ja.js

11 ms

conversion.js

conversion.js

71 ms

v2_common.css

v2_common.css

465 ms

ga.js

ga.js

114 ms

gs_noscript_100-50_ja.gif

gs_noscript_100-50_ja.gif

81 ms

logo.gif

logo.gif

176 ms

banner_tel.gif

banner_tel.gif

175 ms

bt_mailmag.gif

bt_mailmag.gif

175 ms

bg_navi.png

bg_navi.png

173 ms

bg_naviline.gif

bg_naviline.gif

174 ms

navi_air_in.gif

navi_air_in.gif

172 ms

navi_tour_off.gif

navi_tour_off.gif

306 ms

navi_hotel_off.gif

navi_hotel_off.gif

300 ms

navi_package_off.gif

navi_package_off.gif

300 ms

navi_hoken_off.gif

navi_hoken_off.gif

310 ms

navi_kokunai_off.gif

navi_kokunai_off.gif

305 ms

img_h1_title_air.jpg

img_h1_title_air.jpg

450 ms

bg_search-form-box_title_icon.gif

bg_search-form-box_title_icon.gif

445 ms

bt_search.gif

bt_search.gif

446 ms

bt_search3_set.png

bt_search3_set.png

593 ms

img_info_01.jpg

img_info_01.jpg

452 ms

icon_new_001.gif

icon_new_001.gif

456 ms

img_bnr_dp.gif

img_bnr_dp.gif

589 ms

bn_multi-city_240.jpg

bn_multi-city_240.jpg

738 ms

bn_oj_240.jpg

bn_oj_240.jpg

593 ms

bn_os_240.jpg

bn_os_240.jpg

600 ms

top_jataiata.jpg

top_jataiata.jpg

609 ms

top_line.gif

top_line.gif

733 ms

__utm.gif

__utm.gif

60 ms

52 ms

42 ms

36 ms

btn_tab.gif

btn_tab.gif

148 ms

Accessibility Review

airnavi.jp accessibility score

88

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

Links do not have a discernible name

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

airnavi.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

airnavi.jp SEO score

100

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

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 Airnavi.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 Airnavi.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

airnavi.jp

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