Tools & Wizards About Us
neol.jp screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

neol.jp

NeoL Magazine JP

Page Load Speed

5 sec in total

First Response

575 ms

Resources Loaded

4 sec

Page Rendered

430 ms

neol.jp screenshot

About Website

Welcome to neol.jp homepage info - get ready to check NeoL best content for Japan right away, or after learning these important things about neol.jp

クリエイティブ・ソースを探求するインターネット•マガジン。アート、ファッション、ムービー、ミュージックを網羅したオリジナルコンテンツを発信。

Visit neol.jp

Key Findings

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

Performance Metrics

neol.jp performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

neol.jp

575 ms

www.neol.jp

869 ms

flexslider.css

171 ms

styles.css

341 ms

pagenavi-css.css

496 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 81% of them (60 requests) were addressed to the original Neol.jp, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Neol.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.9 kB (2%)

Content Size

4.6 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Neol.jp main page is 4.6 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 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 75.8 kB

  • Original 91.4 kB
  • After minification 89.1 kB
  • After compression 15.5 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 75.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 21 B

  • Original 4.4 MB
  • After minification 4.4 MB

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

JavaScript Optimization

-0%

Potential reduce by 79 B

  • Original 91.2 kB
  • After minification 91.2 kB
  • After compression 91.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

-25%

Potential reduce by 4.0 kB

  • Original 16.3 kB
  • After minification 16.1 kB
  • After compression 12.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. Neol.jp needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (39%)

Requests Now

69

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

neol.jp

neol.jp

575 ms

www.neol.jp

www.neol.jp

869 ms

flexslider.css

flexslider.css

171 ms

styles.css

styles.css

341 ms

pagenavi-css.css

pagenavi-css.css

496 ms

style.css

style.css

499 ms

neol-slider.css

neol-slider.css

509 ms

jquery.js

jquery.js

680 ms

jquery-migrate.min.js

jquery-migrate.min.js

510 ms

external-tracking.min.js

external-tracking.min.js

510 ms

js

js

58 ms

adsbygoogle.js

adsbygoogle.js

171 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

661 ms

scripts.js

scripts.js

662 ms

navigation.js

navigation.js

676 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

676 ms

jquery.mousewheel.js

jquery.mousewheel.js

734 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

852 ms

neol.js

neol.js

853 ms

wp-embed.min.js

wp-embed.min.js

853 ms

slick.min.js

slick.min.js

850 ms

functions.js

functions.js

854 ms

ajax.js

ajax.js

855 ms

html5shiv-printshiv.js

html5shiv-printshiv.js

1015 ms

selectivizr.js

selectivizr.js

1010 ms

css

css

33 ms

analytics.js

analytics.js

96 ms

beacon.js

beacon.js

152 ms

26d8bb1aaae0ca4c5f61fc6767a32743-1690x990.jpg

26d8bb1aaae0ca4c5f61fc6767a32743-1690x990.jpg

816 ms

22ed013a9ec1394d936575eca5a2aaeb.jpg

22ed013a9ec1394d936575eca5a2aaeb.jpg

1013 ms

morita-1860x873.jpg

morita-1860x873.jpg

1003 ms

NeoL_TheAces-1860x818.jpg

NeoL_TheAces-1860x818.jpg

495 ms

50e4e4824c72f483fc9198813c44a3d7-1860x990.jpg

50e4e4824c72f483fc9198813c44a3d7-1860x990.jpg

978 ms

NeoL_cannabis_mimic.jpg

NeoL_cannabis_mimic.jpg

1524 ms

1b3e0f2c0f6a1c7631f2596cae664127-1860x928.jpg

1b3e0f2c0f6a1c7631f2596cae664127-1860x928.jpg

667 ms

fb2788a834ea1a2eabc1212f9c892140-500x390.jpg

fb2788a834ea1a2eabc1212f9c892140-500x390.jpg

837 ms

ed4bf47b2c049e0caf90a27f065e59cb-500x281.jpg

ed4bf47b2c049e0caf90a27f065e59cb-500x281.jpg

981 ms

5eda920316117042fa81a781bc59fc3f-500x271.jpg

5eda920316117042fa81a781bc59fc3f-500x271.jpg

1010 ms

NeoL_oldfo003-500x327.jpg

NeoL_oldfo003-500x327.jpg

1143 ms

a3902fe7537c2951a02a4789dab2572f-500x282.jpg

a3902fe7537c2951a02a4789dab2572f-500x282.jpg

1145 ms

a446ccb3597948332aaad5c05d5bf40c-500x334.jpg

a446ccb3597948332aaad5c05d5bf40c-500x334.jpg

1174 ms

109699bc9b9fe430ea9ffcd59a9b896c-500x333.jpg

109699bc9b9fe430ea9ffcd59a9b896c-500x333.jpg

1181 ms

b1331a1260268b1ab9397a9d1e090fbe-500x304.jpg

b1331a1260268b1ab9397a9d1e090fbe-500x304.jpg

1180 ms

02dca956ea240385b6397c4eefbf3435-500x333.jpg

02dca956ea240385b6397c4eefbf3435-500x333.jpg

1308 ms

fc7fce9f9e88f1cc71546f26335259f0-500x361.jpg

fc7fce9f9e88f1cc71546f26335259f0-500x361.jpg

1309 ms

manuka-honey-vision1_-500x282.jpg

manuka-honey-vision1_-500x282.jpg

1344 ms

46858d1a0336ec61d8a328efc4e6b481-500x355.jpg

46858d1a0336ec61d8a328efc4e6b481-500x355.jpg

1350 ms

meisafujishiro-500x375.jpg

meisafujishiro-500x375.jpg

1350 ms

kyozan_1-500x374.jpg

kyozan_1-500x374.jpg

1472 ms

MeisaFujishiro1-500x375.jpg

MeisaFujishiro1-500x375.jpg

1473 ms

kyozan-500x331.jpg

kyozan-500x331.jpg

1516 ms

NeoL_fujishiro1-500x375.jpg

NeoL_fujishiro1-500x375.jpg

1521 ms

591523999fa26f483977de3bfb020f6b-500x397.jpg

591523999fa26f483977de3bfb020f6b-500x397.jpg

1521 ms

tatsuno3.jpg

tatsuno3.jpg

1638 ms

sdk.js

sdk.js

136 ms

ef05073c924b85b06a10bb3f85a6742f-500x395.jpg

ef05073c924b85b06a10bb3f85a6742f-500x395.jpg

1606 ms

Ouroboros-400x400.png

Ouroboros-400x400.png

1602 ms

collect

collect

15 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

36 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

36 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

46 ms

3801fbac45bddbe49a359f489058fcdf-477x400.jpg

3801fbac45bddbe49a359f489058fcdf-477x400.jpg

1537 ms

loading.gif

loading.gif

1534 ms

e2f7140a1e5088e4894fdd9eeefe8c63-500x282.jpg

e2f7140a1e5088e4894fdd9eeefe8c63-500x282.jpg

1534 ms

75c140d3601436d9bf49d9f8aa3af58a-500x333.jpg

75c140d3601436d9bf49d9f8aa3af58a-500x333.jpg

1645 ms

header_logo.png

header_logo.png

1645 ms

sns.png

sns.png

1703 ms

sdk.js

sdk.js

5 ms

collect

collect

77 ms

js

js

54 ms

56 ms

arrow_right.png

arrow_right.png

1549 ms

arrow_down.png

arrow_down.png

1533 ms

btn_totop.png

btn_totop.png

1371 ms

Accessibility Review

neol.jp accessibility score

58

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.

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

neol.jp best practices score

83

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

SEO Factors

neol.jp SEO score

90

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

neol.jp

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