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

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 77 B

  • Original 87.4 kB
  • After minification 87.4 kB
  • After compression 87.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. 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

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.

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

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: