Tools & Wizards About Us
reginalocus.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

reginalocus.com

顔に自信を勢いを。メンズエイジングケア｜REGINA LOCUS MEN

Page Load Speed

5.2 sec in total

First Response

880 ms

Resources Loaded

3.8 sec

Page Rendered

479 ms

reginalocus.com screenshot

About Website

Click here to check amazing REGINA LOCUS content. Otherwise, check out these important facts you probably never knew about reginalocus.com

全ての戦う男たちへ最も先進的なメンズエイジングケアを。メンズエイジングケアと謳いながら、成分がほとんど配合されていないメンズエイジングケアが溢れる化粧品業界。ネットで調べても出るのはアフェリエイトばかりで、本物の価値を見分けることが難しい時代。一つ言えることは、広告を出しまくっている商品は良いわけがない。なぜなら、広告費にばかりお金をかけ、商品として最も重要な原料にはほとんど予算をさけないからだ。...

Visit reginalocus.com

Key Findings

We analyzed Reginalocus.com page load time and found that the first response time was 880 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

reginalocus.com performance score

0

Network Requests Diagram

reginalocus.com

880 ms

common.css

184 ms

ga.js

13 ms

all.js

11 ms

widgets.js

103 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 27% of them (14 requests) were addressed to the original Reginalocus.com, 16% (8 requests) were made to Apis.google.com and 16% (8 requests) were made to O.twimg.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Reginalocus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 133.3 kB (4%)

Content Size

3.2 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Reginalocus.com main page is 3.2 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 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 16.7 kB

  • Original 23.8 kB
  • After minification 23.3 kB
  • After compression 7.1 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 16.7 kB or 70% of the original size.

Image Optimization

-3%

Potential reduce by 81.6 kB

  • Original 3.1 MB
  • After minification 3.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. REGINA LOCUS images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 6.1 kB

  • Original 27.6 kB
  • After minification 27.6 kB
  • After compression 21.5 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 6.1 kB or 22% of the original size.

CSS Optimization

-84%

Potential reduce by 29.0 kB

  • Original 34.6 kB
  • After minification 33.9 kB
  • After compression 5.7 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. Reginalocus.com needs all CSS files to be minified and compressed as it can save up to 29.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (35%)

Requests Now

49

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

reginalocus.com

reginalocus.com

880 ms

common.css

common.css

184 ms

ga.js

ga.js

13 ms

all.js

all.js

11 ms

widgets.js

widgets.js

103 ms

plusone.js

plusone.js

152 ms

bg.png

bg.png

359 ms

logo.png

logo.png

510 ms

fb.png

fb.png

359 ms

menuborder.png

menuborder.png

357 ms

c_bg.png

c_bg.png

380 ms

LVN.png

LVN.png

1451 ms

ERtop.jpg

ERtop.jpg

1212 ms

RLmen.jpg

RLmen.jpg

1194 ms

whatsfullerenes.jpg

whatsfullerenes.jpg

1021 ms

RLMENgoldenratiomain.png

RLMENgoldenratiomain.png

2729 ms

gotoshop.jpg

gotoshop.jpg

1009 ms

howtoorder.png

howtoorder.png

1181 ms

__utm.gif

__utm.gif

35 ms

170 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

60 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

91 ms

xd_arbiter.php

xd_arbiter.php

58 ms

xd_arbiter.php

xd_arbiter.php

91 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

34 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

61 ms

fastbutton

fastbutton

128 ms

syndication

syndication

154 ms

484049016938721281

484049016938721281

320 ms

postmessageRelay

postmessageRelay

100 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

56 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

72 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

80 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

80 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

59 ms

rpc:shindig_random.js

rpc:shindig_random.js

58 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

proxy.jpg

proxy.jpg

124 ms

proxy.jpg

proxy.jpg

117 ms

proxy.jpg

proxy.jpg

65 ms

proxy.jpg

proxy.jpg

115 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

14 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

17 ms

YF1KK0xO_normal.jpeg

YF1KK0xO_normal.jpeg

106 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

31 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

35 ms

proxy.jpg

proxy.jpg

46 ms

proxy.jpg

proxy.jpg

48 ms

proxy.jpg

proxy.jpg

31 ms

proxy.jpg

proxy.jpg

47 ms

jot.html

jot.html

3 ms

SEO Factors

reginalocus.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reginalocus.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Reginalocus.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

reginalocus.com

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