Tools & Wizards About Us
werentacar.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 85

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

werentacar.com

ハワイレンタカーといえば安心で安全なドライブを提案するホノルルオートレンタルへ

Page Load Speed

3.3 sec in total

First Response

1.1 sec

Resources Loaded

2 sec

Page Rendered

191 ms

werentacar.com screenshot

About Website

Welcome to werentacar.com homepage info - get ready to check Werentacar best content for Japan right away, or after learning these important things about werentacar.com

ハワイで唯一日本人経営のレンタカー会社のホノルルオートレンタル。予約、保険の説明などすべて日本語でOK。親切丁寧に対応します。チャイルドシートや日本語カーナビも装備した日本人観光客に人気のレンタカー会社です。ハワイレンタカーのホノルルオートレンタルはあなたのハワイの足をご用意します。女性・子連れに優しいと口コミで評判。

Visit werentacar.com

Key Findings

We analyzed Werentacar.com page load time and found that the first response time was 1.1 sec and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

werentacar.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value12.9 s

3/100

10%

TBT (Total Blocking Time)

Value1,210 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.28

44/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

werentacar.com

1087 ms

style.css

321 ms

bg_left.jpg

185 ms

n_01.gif

162 ms

n_02.gif

314 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 93% of them (28 requests) were addressed to the original Werentacar.com, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Werentacar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.4 kB (51%)

Content Size

116.9 kB

After Optimization

57.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Werentacar.com main page is 116.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. HTML takes 73.9 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 52.7 kB

  • Original 73.9 kB
  • After minification 72.3 kB
  • After compression 21.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 52.7 kB or 71% of the original size.

Image Optimization

-5%

Potential reduce by 967 B

  • Original 19.1 kB
  • After minification 18.1 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. Werentacar images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-84%

Potential reduce by 5.7 kB

  • Original 6.7 kB
  • After minification 4.7 kB
  • After compression 1.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. Werentacar.com needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (33%)

Requests Now

27

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

werentacar.com

werentacar.com

1087 ms

style.css

style.css

321 ms

bg_left.jpg

bg_left.jpg

185 ms

n_01.gif

n_01.gif

162 ms

n_02.gif

n_02.gif

314 ms

n_03.gif

n_03.gif

324 ms

n_04.gif

n_04.gif

336 ms

n_05.gif

n_05.gif

336 ms

bg_right.jpg

bg_right.jpg

363 ms

ind_car01.jpg

ind_car01.jpg

727 ms

sidemenu01.gif

sidemenu01.gif

471 ms

sidemenu02.gif

sidemenu02.gif

483 ms

sidemenu03.gif

sidemenu03.gif

504 ms

check.gif

check.gif

507 ms

ind_new_ti.gif

ind_new_ti.gif

544 ms

1_r1_c1.gif

1_r1_c1.gif

530 ms

1_r2_c1.jpg

1_r2_c1.jpg

545 ms

1_r2_c3.jpg

1_r2_c3.jpg

572 ms

1_r3_c1.gif

1_r3_c1.gif

576 ms

ind_acc_ti.gif

ind_acc_ti.gif

629 ms

bn_qr.gif

bn_qr.gif

839 ms

ind_acc_img01.gif

ind_acc_img01.gif

705 ms

navi_bn.gif

navi_bn.gif

741 ms

pkg_bn.gif

pkg_bn.gif

910 ms

bn_01.gif

bn_01.gif

810 ms

bn_02.gif

bn_02.gif

812 ms

footer_line.gif

footer_line.gif

866 ms

copyright.gif

copyright.gif

908 ms

ga.js

ga.js

8 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

werentacar.com accessibility score

93

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-hidden="true"] elements contain focusable descendents

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

werentacar.com best practices score

85

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

werentacar.com SEO score

93

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Werentacar.com 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 Werentacar.com main page’s claimed encoding is euc-jp. 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

werentacar.com

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