Tools & Wizards About Us
nanet-hiroshima.com screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

nanet-hiroshima.com

ナレーターズネット広島 広島を中心にフリーランスで活躍するナレーターズサイト！

Page Load Speed

2.6 sec in total

First Response

509 ms

Resources Loaded

2.1 sec

Page Rendered

84 ms

nanet-hiroshima.com screenshot

About Website

Visit nanet-hiroshima.com now to see the best up-to-date Nanet Hiroshima content and also check out these interesting facts you probably never knew about nanet-hiroshima.com

ナレーターズネット広島 広島を中心にフリーランスで活躍するナレーターズサイト！

Visit nanet-hiroshima.com

Key Findings

We analyzed Nanet-hiroshima.com page load time and found that the first response time was 509 ms and then it took 2.1 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

nanet-hiroshima.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

nanet-hiroshima.com

509 ms

import.css

166 ms

SpryData.js

501 ms

xpath.js

512 ms

rss.js

342 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 93% of them (39 requests) were addressed to the original Nanet-hiroshima.com, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Nanet-hiroshima.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.5 kB (12%)

Content Size

224.4 kB

After Optimization

197.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nanet-hiroshima.com main page is 224.4 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. 25% of websites need less resources to load. Images take 145.7 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 4.7 kB

  • Original 7.3 kB
  • After minification 7.2 kB
  • After compression 2.6 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 4.7 kB or 65% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 145.7 kB
  • After minification 145.7 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. Nanet Hiroshima images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 20.9 kB

  • Original 67.6 kB
  • After minification 67.6 kB
  • After compression 46.7 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 20.9 kB or 31% of the original size.

CSS Optimization

-22%

Potential reduce by 832 B

  • Original 3.8 kB
  • After minification 3.8 kB
  • After compression 3.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. Nanet-hiroshima.com needs all CSS files to be minified and compressed as it can save up to 832 B or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (37%)

Requests Now

41

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nanet-hiroshima.com

nanet-hiroshima.com

509 ms

import.css

import.css

166 ms

SpryData.js

SpryData.js

501 ms

xpath.js

xpath.js

512 ms

rss.js

rss.js

342 ms

js

js

55 ms

base.css

base.css

178 ms

style.css

style.css

333 ms

navi.css

navi.css

340 ms

bgline01.gif

bgline01.gif

167 ms

logo.gif

logo.gif

175 ms

ph_main01.jpg

ph_main01.jpg

341 ms

ph_main02.jpg

ph_main02.jpg

341 ms

ph_main03.jpg

ph_main03.jpg

331 ms

btn01_o.jpg

btn01_o.jpg

171 ms

btn01_n.jpg

btn01_n.jpg

331 ms

btn02_o.gif

btn02_o.gif

340 ms

btn02_n.gif

btn02_n.gif

346 ms

btn03_o.gif

btn03_o.gif

497 ms

btn03_n.gif

btn03_n.gif

497 ms

btn04_o.gif

btn04_o.gif

509 ms

btn04_n.gif

btn04_n.gif

511 ms

bnr_hougen01.gif

bnr_hougen01.gif

511 ms

h3_1.gif

h3_1.gif

520 ms

text_lineup01.gif

text_lineup01.gif

661 ms

text_lineup02.gif

text_lineup02.gif

662 ms

text_lineup03.gif

text_lineup03.gif

682 ms

text_lineup04.gif

text_lineup04.gif

681 ms

text_lineup05.gif

text_lineup05.gif

682 ms

text_lineup06.gif

text_lineup06.gif

691 ms

h2_1.gif

h2_1.gif

827 ms

gn_top_o.gif

gn_top_o.gif

827 ms

gn_talent_o.gif

gn_talent_o.gif

852 ms

gn_talent_n.gif

gn_talent_n.gif

880 ms

gn_voice_o.gif

gn_voice_o.gif

853 ms

gn_voice_n.gif

gn_voice_n.gif

862 ms

gn_blog_o.gif

gn_blog_o.gif

991 ms

gn_blog_n.gif

gn_blog_n.gif

992 ms

gn_contact_o.gif

gn_contact_o.gif

1021 ms

gn_contact_n.gif

gn_contact_n.gif

1023 ms

ga.js

ga.js

7 ms

__utm.gif

__utm.gif

27 ms

Accessibility Review

nanet-hiroshima.com accessibility score

90

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

nanet-hiroshima.com best practices score

75

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

nanet-hiroshima.com SEO score

75

Search Engine Optimization Advices

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 Nanet-hiroshima.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 Nanet-hiroshima.com 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

nanet-hiroshima.com

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