16.7 sec in total
501 ms
15.6 sec
603 ms
Visit someone.jp now to see the best up-to-date Someone content and also check out these interesting facts you probably never knew about someone.jp
Visit someone.jpWe analyzed Someone.jp page load time and found that the first response time was 501 ms and then it took 16.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
someone.jp performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value5.8 s
15/100
25%
Value6.6 s
38/100
10%
Value550 ms
54/100
30%
Value0.106
88/100
15%
Value10.1 s
26/100
10%
501 ms
1089 ms
67 ms
79 ms
1103 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 86% of them (54 requests) were addressed to the original Someone.jp, 11% (7 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (10.3 sec) belongs to the original domain Someone.jp.
Page size can be reduced by 1.4 MB (18%)
7.9 MB
6.5 MB
In fact, the total size of Someone.jp main page is 7.9 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. 30% of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.
Potential reduce by 41.4 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 41.4 kB or 81% of the original size.
Potential reduce by 257.0 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. Someone images are well optimized though.
Potential reduce by 1.1 MB
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 needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 90% of the original size.
Number of requests can be reduced by 13 (25%)
53
40
The browser has sent 53 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 8 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
someone.jp
501 ms
someone.jp
1089 ms
css
67 ms
css
79 ms
style.css
1103 ms
author-profile-widget.css
1093 ms
frontend.css
1152 ms
js_composer.min.css
1835 ms
style.css
2173 ms
jquery-1.4.2.min.js
40 ms
main.js
2615 ms
jquery.cookie.min.js
2067 ms
tagdiv_theme.min.js
2596 ms
comment-reply.min.js
2224 ms
wp-embed.min.js
2843 ms
js_composer_front.min.js
3160 ms
wp-emoji-release.min.js
992 ms
someone272_031.png
1047 ms
someone230_031.png
1073 ms
someone32.jpg
1987 ms
someone31.jpg
1924 ms
someone30.jpg
2644 ms
someone29.jpg
3232 ms
someone28.jpg
3029 ms
someone27.jpg
1076 ms
someone26.jpg
3236 ms
someone25.jpg
3798 ms
someone24.jpg
3950 ms
130306_someone23_Lindoc-212x300.jpg
3874 ms
someone22_cover-212x300.png
5115 ms
cover_21.jpg
6224 ms
4d11bae980b302efa9d9cab602e1f325.jpg
4462 ms
cover_192.jpg
6635 ms
695ee2ec7f2ce2845dbb2da772c7d51b.jpg
6377 ms
2011autumn.jpeg
5928 ms
2011summer.jpeg
5707 ms
item.jpeg
6892 ms
20110104-someone14_cover.jpeg
7054 ms
20100927-someone13_cover.jpeg
7162 ms
20100707-someone_12_cover.jpeg
7408 ms
vol11.jpeg
9489 ms
20091215-cover_10_cut.jpeg
9101 ms
20090917-cover09.jpeg
7876 ms
20090531-cover_08s.jpeg
8853 ms
20090123-cover07_small.jpeg
7164 ms
20081007-cover06.jpeg
8648 ms
20080520-cover05.jpeg
7412 ms
20080128-cover04_web.jpeg
7660 ms
20070918-cover03.jpeg
8629 ms
20070920-cover02.jpeg
9455 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
49 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
62 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
89 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
103 ms
Zd2E9abXLFGSr9G3YK2MsMEHkXu385rSv8spHqOuvSI.ttf
102 ms
b9QBgL0iMZfDSpmcXcE8nBPtpc1JAjij63Hi_JcAPQ4.ttf
102 ms
b9QBgL0iMZfDSpmcXcE8nPVE82mBoqAQeMZO1WdebIw.ttf
103 ms
newsmag.svg
9906 ms
newsmag.woff
9118 ms
20070920-cover01.jpeg
9252 ms
20070920-cover00.jpeg
9535 ms
someonetest.jpg
10295 ms
someoneWhite_03.png
9425 ms
someone.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
someone.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
someone.jp SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
EN
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 does not match the claimed English 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.
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: