Tools & Wizards About Us
g-legend.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

g-legend.jp

「銀座レジェンド」東京高級デリヘル 銀座発デリヘル – 銀座発デリヘル 「銀座レジェンド」東京高級デリヘル

Page Load Speed

10.4 sec in total

First Response

807 ms

Resources Loaded

8.8 sec

Page Rendered

776 ms

g-legend.jp screenshot

About Website

Visit g-legend.jp now to see the best up-to-date G Legend content and also check out these interesting facts you probably never knew about g-legend.jp

銀座Legend レジェンドは皆様に「美しさ」と「ときめき」をデリバリーします　いつまでも語り継がれ、皆様から愛されるデリバリーヘルス店になる事を目標に「レ ジェンド」は生まれました。レジェンドは皆様に「美しさ」と「ときめき」をデリバリー致します。

Visit g-legend.jp

Key Findings

We analyzed G-legend.jp page load time and found that the first response time was 807 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

g-legend.jp performance score

0

Network Requests Diagram

g-legend.jp

807 ms

layout.css

419 ms

general.css

614 ms

index.css

616 ms

element.js

44 ms

Our browser made a total of 158 requests to load all elements on the main page. We found that 26% of them (41 requests) were addressed to the original G-legend.jp, 12% (19 requests) were made to H-fan.net and 8% (12 requests) were made to Delicon.mm-mv.net. The less responsive or slowest element that took the longest time to load (6.6 sec) relates to the external source Lovehomap.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 94.0 kB (25%)

Content Size

375.3 kB

After Optimization

281.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of G-legend.jp main page is 375.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 229.6 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 9.1 kB

  • Original 14.5 kB
  • After minification 14.3 kB
  • After compression 5.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 9.1 kB or 63% of the original size.

Image Optimization

-27%

Potential reduce by 61.0 kB

  • Original 229.6 kB
  • After minification 168.6 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. Obviously, G Legend needs image optimization as it can save up to 61.0 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 804 B

  • Original 99.9 kB
  • After minification 99.9 kB
  • After compression 99.0 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

-74%

Potential reduce by 23.1 kB

  • Original 31.4 kB
  • After minification 22.8 kB
  • After compression 8.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. G-legend.jp needs all CSS files to be minified and compressed as it can save up to 23.1 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (40%)

Requests Now

148

After Optimization

89

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

g-legend.jp

g-legend.jp

807 ms

layout.css

layout.css

419 ms

general.css

general.css

614 ms

index.css

index.css

616 ms

element.js

element.js

44 ms

body_bg.jpg

body_bg.jpg

945 ms

main_img.jpg

main_img.jpg

1983 ms

enter.gif

enter.gif

247 ms

exit.gif

exit.gif

246 ms

l_box_top.gif

l_box_top.gif

454 ms

imgtext01.gif

imgtext01.gif

454 ms

imgtext02.gif

imgtext02.gif

453 ms

l_box_bottom.gif

l_box_bottom.gif

453 ms

r_box_top.gif

r_box_top.gif

560 ms

index-recruit.jpg

index-recruit.jpg

1251 ms

r_box_bottom.gif

r_box_bottom.gif

559 ms

h2_img01.jpg

h2_img01.jpg

723 ms

info_bg_top01.gif

info_bg_top01.gif

733 ms

info_bg_bottom01.gif

info_bg_bottom01.gif

734 ms

translateelement.css

translateelement.css

147 ms

main.js

main.js

221 ms

toplink.html

toplink.html

1281 ms

ga.js

ga.js

82 ms

l_box_bg.gif

l_box_bg.gif

759 ms

r_box_bg.gif

r_box_bg.gif

759 ms

info_bg.gif

info_bg.gif

945 ms

element_main.js

element_main.js

77 ms

__utm.gif

__utm.gif

28 ms

collect

collect

143 ms

translate_24dp.png

translate_24dp.png

55 ms

l

l

50 ms

googlelogo_color_68x28dp.png

googlelogo_color_68x28dp.png

34 ms

cleardot.gif

cleardot.gif

52 ms

te_ctrl3.gif

te_ctrl3.gif

31 ms

loading.gif

loading.gif

31 ms

toplink.css

toplink.css

213 ms

bana.css

bana.css

577 ms

town_banner_468x60_b1.gif

town_banner_468x60_b1.gif

810 ms

fuzokujapan468-60.gif

fuzokujapan468-60.gif

495 ms

468x60.gif

468x60.gif

6626 ms

b1.gif

b1.gif

781 ms

town_banner_468x60_b2.gif

town_banner_468x60_b2.gif

806 ms

town_banner_468x60_b3.gif

town_banner_468x60_b3.gif

824 ms

town_banner_468x60_b4.gif

town_banner_468x60_b4.gif

819 ms

town_banner_468x60_b5.gif

town_banner_468x60_b5.gif

834 ms

town_banner_468x60_b6_2.gif

town_banner_468x60_b6_2.gif

834 ms

town_banner_468x60_b7_2.gif

town_banner_468x60_b7_2.gif

991 ms

town_banner_468x60_b8_2.gif

town_banner_468x60_b8_2.gif

991 ms

town_banner_468x60_b9.gif

town_banner_468x60_b9.gif

1007 ms

b2.gif

b2.gif

566 ms

bt_logo.gif

bt_logo.gif

572 ms

bt_01.gif

bt_01.gif

577 ms

bt_02.gif

bt_02.gif

589 ms

bt_03.gif

bt_03.gif

591 ms

bt_04.gif

bt_04.gif

582 ms

bt_05.gif

bt_05.gif

965 ms

bt_06.gif

bt_06.gif

986 ms

bt_07.gif

bt_07.gif

970 ms

bt_08.gif

bt_08.gif

986 ms

bt_09.gif

bt_09.gif

987 ms

sp2-1.gif

sp2-1.gif

750 ms

468_60.gif

468_60.gif

1596 ms

town_banner_468x60_n1.gif

town_banner_468x60_n1.gif

680 ms

newface_sp_bner_01.jpg

newface_sp_bner_01.jpg

549 ms

delisoku_banner_228-60.gif

delisoku_banner_228-60.gif

734 ms

delisoku_banner_60-30_01.gif

delisoku_banner_60-30_01.gif

577 ms

delisoku_banner_60-30_02.gif

delisoku_banner_60-30_02.gif

584 ms

delisoku_banner_60-30_03.gif

delisoku_banner_60-30_03.gif

585 ms

sp2-2.gif

sp2-2.gif

559 ms

sp2-3.gif

sp2-3.gif

563 ms

sp2-4.gif

sp2-4.gif

571 ms

sp2-5.gif

sp2-5.gif

571 ms

sp2-6.gif

sp2-6.gif

599 ms

sp2-7.gif

sp2-7.gif

900 ms

sp2-8.gif

sp2-8.gif

914 ms

sp2-9.gif

sp2-9.gif

913 ms

sp2-10.gif

sp2-10.gif

917 ms

sp2-11.gif

sp2-11.gif

944 ms

sp2-12.gif

sp2-12.gif

1100 ms

sp2-13.gif

sp2-13.gif

1265 ms

sp2-14.gif

sp2-14.gif

1265 ms

sp2-15.gif

sp2-15.gif

1273 ms

sp2-16.gif

sp2-16.gif

1288 ms

sp2-17.gif

sp2-17.gif

1300 ms

sp2-18.gif

sp2-18.gif

1471 ms

sp2-19.gif

sp2-19.gif

1638 ms

newface_sp_bner_02.jpg

newface_sp_bner_02.jpg

417 ms

newface_sp_bner_03.jpg

newface_sp_bner_03.jpg

411 ms

newface_sp_bner_04.jpg

newface_sp_bner_04.jpg

436 ms

newface_sp_bner_05.jpg

newface_sp_bner_05.jpg

438 ms

newface_sp_bner_06.jpg

newface_sp_bner_06.jpg

442 ms

newface_sp_bner_07.jpg

newface_sp_bner_07.jpg

618 ms

newface_sp_bner_08.jpg

newface_sp_bner_08.jpg

617 ms

newface_sp_bner_09.jpg

newface_sp_bner_09.jpg

646 ms

newface_sp_bner_10.jpg

newface_sp_bner_10.jpg

646 ms

b3.gif

b3.gif

387 ms

b4.gif

b4.gif

396 ms

tokyo468-60.gif

tokyo468-60.gif

582 ms

town_banner_468x60_n2.gif

town_banner_468x60_n2.gif

651 ms

town_banner_468x60_n3.gif

town_banner_468x60_n3.gif

652 ms

town_banner_468x60_n4.gif

town_banner_468x60_n4.gif

656 ms

town_banner_468x60_n5.gif

town_banner_468x60_n5.gif

653 ms

town_banner_468x60_n6.gif

town_banner_468x60_n6.gif

655 ms

town_banner_468x60_n7.gif

town_banner_468x60_n7.gif

956 ms

town_banner_468x60_n8.gif

town_banner_468x60_n8.gif

959 ms

town_banner_468x60_n9.gif

town_banner_468x60_n9.gif

957 ms

btnfull-1_01.gif

btnfull-1_01.gif

569 ms

spadbanners.css

spadbanners.css

521 ms

fuzoku-m468.gif

fuzoku-m468.gif

1070 ms

navi_468_2.gif

navi_468_2.gif

613 ms

dl-cityfor1.gif

dl-cityfor1.gif

798 ms

banner2.jpg

banner2.jpg

951 ms

dj88_31b.gif

dj88_31b.gif

589 ms

deli_88.gif

deli_88.gif

994 ms

btnfull-1_02.gif

btnfull-1_02.gif

569 ms

btnfull-1_03.gif

btnfull-1_03.gif

606 ms

btnfull-1_04.gif

btnfull-1_04.gif

587 ms

btnfull-1_05.gif

btnfull-1_05.gif

614 ms

btnfull-1_06.gif

btnfull-1_06.gif

616 ms

btnfull-1_07.gif

btnfull-1_07.gif

925 ms

hcdeli46860.png

hcdeli46860.png

956 ms

link02.gif

link02.gif

371 ms

link04.gif

link04.gif

185 ms

link05.gif

link05.gif

370 ms

link06.gif

link06.gif

732 ms

link07.gif

link07.gif

560 ms

link08.gif

link08.gif

711 ms

link09.gif

link09.gif

786 ms

link11.gif

link11.gif

882 ms

link12.jpg

link12.jpg

899 ms

tokyo88-31.gif

tokyo88-31.gif

886 ms

d24_88x31_2.gif

d24_88x31_2.gif

1086 ms

100-30.gif

100-30.gif

1161 ms

sb_88x31%20(1).gif

sb_88x31%20(1).gif

1054 ms

link13.gif

link13.gif

1479 ms

banner.gif

banner.gif

2336 ms

link14.gif

link14.gif

1112 ms

dl-cityfor2.gif

dl-cityfor2.gif

785 ms

dl-cityfor3.gif

dl-cityfor3.gif

607 ms

dl-cityfor4.gif

dl-cityfor4.gif

615 ms

delisoku_banner_60-30_04.gif

delisoku_banner_60-30_04.gif

381 ms

delisoku_banner_60-30_05.gif

delisoku_banner_60-30_05.gif

390 ms

delisoku_banner_60-30_06.gif

delisoku_banner_60-30_06.gif

577 ms

delisoku_banner_60-30_07.gif

delisoku_banner_60-30_07.gif

586 ms

delisoku_banner_60-30_08.gif

delisoku_banner_60-30_08.gif

584 ms

sp_banner_delicon_01.gif

sp_banner_delicon_01.gif

641 ms

sp_banner_delicon_02.gif

sp_banner_delicon_02.gif

481 ms

sp_banner_delicon_03.gif

sp_banner_delicon_03.gif

523 ms

sp_banner_delicon_04.gif

sp_banner_delicon_04.gif

510 ms

sp_banner_delicon_05.gif

sp_banner_delicon_05.gif

504 ms

sp_banner_delicon_06.gif

sp_banner_delicon_06.gif

620 ms

sp_banner_delicon_07.gif

sp_banner_delicon_07.gif

619 ms

sp_banner_delicon_08.gif

sp_banner_delicon_08.gif

639 ms

sp_banner_delicon_09.gif

sp_banner_delicon_09.gif

654 ms

sp_banner_delicon_10.gif

sp_banner_delicon_10.gif

658 ms

sp_banner_delicon_11.gif

sp_banner_delicon_11.gif

766 ms

bt_background.png

bt_background.png

373 ms

www.fuzoku-m.com

www.fuzoku-m.com

736 ms

SEO Factors

g-legend.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise G-legend.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 G-legend.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

g-legend.jp

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