Tools & Wizards About Us
n-hoolywood.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

n-hoolywood.com

N-HOOLYWOOD.COM

Page Load Speed

2.9 sec in total

First Response

306 ms

Resources Loaded

2.2 sec

Page Rendered

386 ms

n-hoolywood.com screenshot

About Website

Click here to check amazing N HOOLYWOOD content for Japan. Otherwise, check out these important facts you probably never knew about n-hoolywood.com

Official brand site & online store. N.HOOLYWOOD | Mister hollywood co., ltd.

Visit n-hoolywood.com

Key Findings

We analyzed N-hoolywood.com page load time and found that the first response time was 306 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

n-hoolywood.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value22.2 s

0/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value2,340 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

n-hoolywood.tumblr.com

306 ms

pre_tumblelog.js

15 ms

css

29 ms

tumblelog_post_message_queue.js

12 ms

stylesheet.css

12 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 38% of them (30 requests) were addressed to the original N-hoolywood.com, 12% (9 requests) were made to Assets.tumblr.com and 9% (7 requests) were made to 41.media.tumblr.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain N-hoolywood.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 846.5 kB (40%)

Content Size

2.1 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of N-hoolywood.com main page is 2.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. 55% of websites need less resources to load. Images take 993.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 72.6 kB

  • Original 86.6 kB
  • After minification 81.2 kB
  • After compression 14.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 72.6 kB or 84% of the original size.

Image Optimization

-9%

Potential reduce by 90.3 kB

  • Original 993.7 kB
  • After minification 903.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. N HOOLYWOOD images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 481.0 kB

  • Original 783.3 kB
  • After minification 773.4 kB
  • After compression 302.3 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 481.0 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 202.7 kB

  • Original 244.3 kB
  • After minification 244.1 kB
  • After compression 41.6 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. N-hoolywood.com needs all CSS files to be minified and compressed as it can save up to 202.7 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

73

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

n-hoolywood.tumblr.com

n-hoolywood.tumblr.com

306 ms

pre_tumblelog.js

pre_tumblelog.js

15 ms

css

css

29 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

12 ms

stylesheet.css

stylesheet.css

12 ms

jquery.min.js

jquery.min.js

54 ms

globalmenu.js

globalmenu.js

579 ms

blocksit.js

blocksit.js

427 ms

jquery.easing.js

jquery.easing.js

440 ms

jquery.cookie.js

jquery.cookie.js

439 ms

index.js

index.js

13 ms

bg_news.png

bg_news.png

362 ms

tumblr_o38t9nfP5K1sikz4co1_500.jpg

tumblr_o38t9nfP5K1sikz4co1_500.jpg

176 ms

like_iframe.html

like_iframe.html

46 ms

vj9rpv7cS_4

vj9rpv7cS_4

132 ms

tumblr_o1ujj3CwJe1sikz4co1_500.jpg

tumblr_o1ujj3CwJe1sikz4co1_500.jpg

65 ms

tumblr_o1raafkc3P1sikz4co1_500.jpg

tumblr_o1raafkc3P1sikz4co1_500.jpg

353 ms

tumblr_nyyu1xppWr1sikz4co1_500.png

tumblr_nyyu1xppWr1sikz4co1_500.png

138 ms

tumblr_ny73r4UlAT1sikz4co1_500.png

tumblr_ny73r4UlAT1sikz4co1_500.png

156 ms

tumblr_nxj1sskaAX1sikz4co1_500.jpg

tumblr_nxj1sskaAX1sikz4co1_500.jpg

162 ms

tumblr_nx617lJWnU1sikz4co1_500.jpg

tumblr_nx617lJWnU1sikz4co1_500.jpg

139 ms

tumblr_nx609eG5wz1sikz4co1_500.png

tumblr_nx609eG5wz1sikz4co1_500.png

272 ms

bg_daily.png

bg_daily.png

339 ms

bg_collection.png

bg_collection.png

341 ms

bg_commingsoon.png

bg_commingsoon.png

347 ms

bg_usw.png

bg_usw.png

348 ms

bg_store.png

bg_store.png

376 ms

bg_information.png

bg_information.png

701 ms

header_v.png

header_v.png

701 ms

bg_header2.png

bg_header2.png

701 ms

logo-loading.gif

logo-loading.gif

444 ms

btn_slidedown.png

btn_slidedown.png

445 ms

btn_t_search.png

btn_t_search.png

734 ms

bk_t_search.gif

bk_t_search.gif

736 ms

logo.png

logo.png

736 ms

btn_facebook.png

btn_facebook.png

771 ms

btn_twitter.png

btn_twitter.png

776 ms

btn_pintarest.png

btn_pintarest.png

867 ms

btn_instagram.png

btn_instagram.png

1026 ms

icon_reblog.png

icon_reblog.png

1075 ms

bk_notecount.png

bk_notecount.png

1078 ms

icon_facebook.png

icon_facebook.png

1079 ms

icon_twitter.png

icon_twitter.png

1084 ms

icon_pin.png

icon_pin.png

1181 ms

btn_old2.jpg

btn_old2.jpg

1330 ms

tumblr_o08010uXxo1sikz4co1_500.jpg

tumblr_o08010uXxo1sikz4co1_500.jpg

27 ms

tumblr_nzhze2CgsU1sikz4co1_500.jpg

tumblr_nzhze2CgsU1sikz4co1_500.jpg

29 ms

tumblr_nxldjw4PKm1sikz4co1_500.png

tumblr_nxldjw4PKm1sikz4co1_500.png

31 ms

tumblr_nxj1plPuQB1sikz4co1_500.jpg

tumblr_nxj1plPuQB1sikz4co1_500.jpg

74 ms

tumblr_nx60r4ZDvb1sikz4co1_500.jpg

tumblr_nx60r4ZDvb1sikz4co1_500.jpg

28 ms

tumblr_nwg3xydkP01sikz4co1_500.jpg

tumblr_nwg3xydkP01sikz4co1_500.jpg

30 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

61 ms

www-embed-player.js

www-embed-player.js

105 ms

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

32 ms

ad_status.js

ad_status.js

81 ms

b9QBgL0iMZfDSpmcXcE8nPVE82mBoqAQeMZO1WdebIw.ttf

b9QBgL0iMZfDSpmcXcE8nPVE82mBoqAQeMZO1WdebIw.ttf

34 ms

5Yl2vTgdty6AzMt12VYvSgLUuEpTyoUstqEm5AMlJo4.ttf

5Yl2vTgdty6AzMt12VYvSgLUuEpTyoUstqEm5AMlJo4.ttf

79 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

89 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

99 ms

ga.js

ga.js

71 ms

vj9rpv7cS_4

vj9rpv7cS_4

89 ms

impixu

impixu

89 ms

impixu

impixu

82 ms

logo_bk.png

logo_bk.png

779 ms

btn_slideup.png

btn_slideup.png

798 ms

analytics.html

analytics.html

122 ms

login_check.html

login_check.html

28 ms

__utm.gif

__utm.gif

74 ms

avatar_110a4c120e2d_40.png

avatar_110a4c120e2d_40.png

75 ms

iframe_logo.png

iframe_logo.png

41 ms

rapid-3.33.js

rapid-3.33.js

49 ms

rapidworker-1.2.js

rapidworker-1.2.js

46 ms

ga.js

ga.js

81 ms

analytics.js

analytics.js

66 ms

cs.js

cs.js

32 ms

yql

yql

227 ms

__utm.gif

__utm.gif

12 ms

cedexis.radar.js

cedexis.radar.js

8 ms

Accessibility Review

n-hoolywood.com accessibility score

70

Accessibility Issues

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

Image elements do not have [alt] attributes

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

n-hoolywood.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

n-hoolywood.com SEO score

62

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise N-hoolywood.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that N-hoolywood.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

n-hoolywood.com

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