Tools & Wizards About Us
arunke.biz screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

arunke.biz

金沢市の地域情報を発信するポータルサイト|あるんけ金沢

Page Load Speed

6.1 sec in total

First Response

698 ms

Resources Loaded

5.3 sec

Page Rendered

138 ms

arunke.biz screenshot

About Website

Visit arunke.biz now to see the best up-to-date Arunke content for Japan and also check out these interesting facts you probably never knew about arunke.biz

あるんけ金沢は地元情報・地域密着のポータルサイトです。金沢近郊のお店の情報、お店からのお知らせを掲載しています。

Visit arunke.biz

Key Findings

We analyzed Arunke.biz page load time and found that the first response time was 698 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

arunke.biz performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.502

16/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

arunke.biz

698 ms

www.arunke.biz

1758 ms

ark_screen.css

752 ms

AC_RunActiveContent.js

539 ms

conan

954 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 57% of them (26 requests) were addressed to the original Arunke.biz, 30% (14 requests) were made to Common.arunke.biz and 13% (6 requests) were made to Sv3.logmill.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Arunke.biz.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.1 kB (11%)

Content Size

350.9 kB

After Optimization

313.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Arunke.biz main page is 350.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. Images take 308.7 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 6.5 kB

  • Original 9.6 kB
  • After minification 8.7 kB
  • After compression 3.1 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 6.5 kB or 68% of the original size.

Image Optimization

-2%

Potential reduce by 5.3 kB

  • Original 308.7 kB
  • After minification 303.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. Arunke images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 7.4 kB

  • Original 11.4 kB
  • After minification 10.0 kB
  • After compression 4.0 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 7.4 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 17.9 kB

  • Original 21.2 kB
  • After minification 12.5 kB
  • After compression 3.3 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. Arunke.biz needs all CSS files to be minified and compressed as it can save up to 17.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (36%)

Requests Now

44

After Optimization

28

  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Arunke. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

arunke.biz

arunke.biz

698 ms

www.arunke.biz

www.arunke.biz

1758 ms

ark_screen.css

ark_screen.css

752 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

539 ms

conan

conan

954 ms

doyle

doyle

1018 ms

ark_lyt_s.css

ark_lyt_s.css

788 ms

ark_orgnl_s.css

ark_orgnl_s.css

367 ms

3_124996795770751300.png

3_124996795770751300.png

538 ms

hd_bc.gif

hd_bc.gif

196 ms

gm_bc.gif

gm_bc.gif

180 ms

gm_line.gif

gm_line.gif

322 ms

gm_btn_bc.gif

gm_btn_bc.gif

361 ms

main_bc.gif

main_bc.gif

361 ms

pg_pgtop.gif

pg_pgtop.gif

391 ms

ft_bc.gif

ft_bc.gif

391 ms

ft_cp_bc.gif

ft_cp_bc.gif

410 ms

1_138330040158832600.png

1_138330040158832600.png

360 ms

1_138330037369105200.png

1_138330037369105200.png

462 ms

1_136920687967918900.jpg

1_136920687967918900.jpg

509 ms

1_135104746980077600.jpg

1_135104746980077600.jpg

510 ms

1_132134605946654400.gif

1_132134605946654400.gif

361 ms

1_129983506071505800.gif

1_129983506071505800.gif

539 ms

1_124420946910943000.jpg

1_124420946910943000.jpg

897 ms

1_130396520244740000.jpg

1_130396520244740000.jpg

768 ms

1_124409306661277400.gif

1_124409306661277400.gif

678 ms

1_124626712346892600.jpg

1_124626712346892600.jpg

679 ms

1_139392841224505100.jpg

1_139392841224505100.jpg

1246 ms

1_139392756515101000.png

1_139392756515101000.png

895 ms

1_127477926950326800.jpg

1_127477926950326800.jpg

1016 ms

1_129800212756852500.jpg

1_129800212756852500.jpg

1015 ms

1_129965342366652300.gif

1_129965342366652300.gif

921 ms

1_129471031662548300.gif

1_129471031662548300.gif

1077 ms

1_130369093840516600.jpg

1_130369093840516600.jpg

1076 ms

1_132728909629465100.gif

1_132728909629465100.gif

1074 ms

1_130396663347832500.jpg

1_130396663347832500.jpg

1355 ms

1_130145744446214400.jpg

1_130145744446214400.jpg

1353 ms

1_124997003996170700.jpg

1_124997003996170700.jpg

1228 ms

1_130396688567982300.jpg

1_130396688567982300.jpg

1432 ms

incoco

incoco

204 ms

watson

watson

205 ms

ark_print.css

ark_print.css

198 ms

inpopo

inpopo

203 ms

ark_lyt_p.css

ark_lyt_p.css

197 ms

ark_orgnl_p.css

ark_orgnl_p.css

182 ms

popo

popo

974 ms

Accessibility Review

arunke.biz accessibility score

85

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

arunke.biz best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

arunke.biz SEO score

92

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

Content Best Practices

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

Impact

Issue

High

Document uses plugins

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 Arunke.biz 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 Arunke.biz 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

arunke.biz

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