Access someone.jp. someone

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,620 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.303

39/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

someone.jp

436 ms

someone.jp

657 ms

1438 ms

ionicons.min.css

88 ms

socialicon.css

34 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Someone.jp, 87% (92 requests) were made to Lne.st and 6% (6 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (10 sec) relates to the external source Lne.st.

Content Size

37.5 MB

After Optimization

37.2 MB

In fact, the total size of Someone.jp main page is 37.5 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. 70% of websites need less resources to load. Images take 37.1 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 207.9 kB

Original 232.0 kB
After minification 231.7 kB
After compression 24.2 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 207.9 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 127.0 kB

Original 37.1 MB
After minification 37.0 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. Someone images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 338 B

Original 38.6 kB
After minification 38.6 kB
After compression 38.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

-6%

Potential reduce by 6.0 kB

Original 100.3 kB
After minification 98.3 kB
After compression 94.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. Someone.jp has all CSS files already compressed.

Requests Now

102

After Optimization

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

Accessibility Issues

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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/).

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 Someone.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 Someone.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

someone.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

someone | リバネス

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

someone.jp

someone.jp

ionicons.min.css

socialicon.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

someone.jp

someone.jp

ionicons.min.css

socialicon.css

style.css

pardot-trace-base.min.js

js

style.min.css

mediaelementplayer-legacy.min.css

wp-mediaelement.min.css

sb-type-std.css

sb-type-fb.css

sb-type-fb-flat.css

sb-type-ln.css

sb-type-ln-flat.css

sb-type-pink.css

sb-type-rtail.css

sb-type-drop.css

sb-type-think.css

sb-no-br.css

js_composer.min.css

jetpack.css

frontend-gtag.js

jquery.min.js

jquery-migrate.min.js

dlm-xhr.min.js

intersection-observer.js

lazy-images.js

e-202424.js

js_composer_front.min.js

contents.js

gtm.js

LeaveaNest_logo_header.png

someone_67_2406-676x960.png

someone66_2403-680x960.jpg

someone65-680x960.jpg

someone64-680x960.jpg

someone63-680x960.jpg

someone62-680x960.jpg

someone61-680x960.jpg

someone60-680x960.jpg

someone59-681x960.jpg

someone58-680x960.jpg

someone57-680x960.jpg