Tools & Wizards About Us
guppy.jp screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

guppy.jp

グッピー｜医療 介護 福祉の求人・転職・給与

Page Load Speed

14.8 sec in total

First Response

346 ms

Resources Loaded

7 sec

Page Rendered

7.5 sec

guppy.jp screenshot

About Website

Visit guppy.jp now to see the best up-to-date Guppy content for Japan and also check out these interesting facts you probably never knew about guppy.jp

グッピー（guppy）は看護師、薬剤師、歯科医師、歯科衛生士、医療事務、介護職など医療介護福祉に特化した求人サイトです。正社員・常勤・パートなど最新の募集情報をご紹介。イベント情報や適性診断など多面的に転職活動を応援します。

Visit guppy.jp

Key Findings

We analyzed Guppy.jp page load time and found that the first response time was 346 ms and then it took 14.5 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

guppy.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value2,460 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

guppy.jp

346 ms

www.guppy.jp

1912 ms

gtm.js

65 ms

top.css

220 ms

iziModal.css

341 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 26% of them (25 requests) were addressed to the original Guppy.jp, 9% (9 requests) were made to App.chatplus.jp and 7% (7 requests) were made to Appimg.chatplus.jp. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Guppy.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 441.9 kB (51%)

Content Size

864.6 kB

After Optimization

422.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Guppy.jp main page is 864.6 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. 65% of websites need less resources to load. HTML takes 402.3 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 357.2 kB

  • Original 402.3 kB
  • After minification 251.7 kB
  • After compression 45.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. This page needs HTML code to be minified as it can gain 150.6 kB, which is 37% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 357.2 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 47.2 kB
  • After minification 47.2 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. Guppy images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 83.7 kB

  • Original 318.1 kB
  • After minification 317.5 kB
  • After compression 234.4 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 83.7 kB or 26% of the original size.

CSS Optimization

-1%

Potential reduce by 952 B

  • Original 97.0 kB
  • After minification 96.8 kB
  • After compression 96.0 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. Guppy.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 75 (82%)

Requests Now

92

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

guppy.jp

guppy.jp

346 ms

www.guppy.jp

www.guppy.jp

1912 ms

gtm.js

gtm.js

65 ms

top.css

top.css

220 ms

iziModal.css

iziModal.css

341 ms

iziToast.css

iziToast.css

501 ms

common.css

common.css

673 ms

jquery.min.js

jquery.min.js

20 ms

slidebars.min.js

slidebars.min.js

502 ms

jquery.cookie.js

jquery.cookie.js

502 ms

lazyload.min.js

lazyload.min.js

507 ms

iziModal.js

iziModal.js

509 ms

iziToast.min.js

iziToast.min.js

661 ms

guppy_sp.js

guppy_sp.js

1171 ms

main.js

main.js

1168 ms

alert_to_obsolete_uas.js

alert_to_obsolete_uas.js

1169 ms

desire_workplace_modal.js

desire_workplace_modal.js

1169 ms

DkYC18o8Mk471xStqF1r.js

DkYC18o8Mk471xStqF1r.js

158 ms

js

js

30 ms

destination

destination

87 ms

index-bg.jpg

index-bg.jpg

350 ms

img_gekkeikan_left.svg

img_gekkeikan_left.svg

350 ms

img_gekkeikan_right.svg

img_gekkeikan_right.svg

348 ms

img_crown.svg

img_crown.svg

352 ms

icon-hatena.svg

icon-hatena.svg

352 ms

lorder-spacer.svg

lorder-spacer.svg

353 ms

bg-pattern.gif

bg-pattern.gif

355 ms

footer_service_links_logo.svg

footer_service_links_logo.svg

356 ms

footer_service_links_privacy.png

footer_service_links_privacy.png

355 ms

uwt.js

uwt.js

357 ms

lt.js

lt.js

355 ms

icomoon.ttf

icomoon.ttf

256 ms

js

js

569 ms

ytag.js

ytag.js

1107 ms

bat.js

bat.js

565 ms

destination

destination

499 ms

js

js

640 ms

pixel.js

pixel.js

698 ms

pixel2.js

pixel2.js

696 ms

pixel2_p_delay.js

pixel2_p_delay.js

696 ms

sc-web-access-analysis.js

sc-web-access-analysis.js

626 ms

itm.js

itm.js

626 ms

err.gif

err.gif

807 ms

err.gif

err.gif

792 ms

adsct

adsct

395 ms

adsct

adsct

327 ms

V9eWqG

V9eWqG

229 ms

segment

segment

342 ms

ld.js

ld.js

25 ms

p

p

678 ms

smallest.png

smallest.png

47 ms

syncframe

syncframe

30 ms

cp.js

cp.js

696 ms

integrate.js

integrate.js

688 ms

event

event

713 ms

gtm.js

gtm.js

37 ms

script.js

script.js

869 ms

log.2.js

log.2.js

18 ms

180 ms

targeting

targeting

153 ms

im-uid.js

im-uid.js

27 ms

tracker

tracker

264 ms

get

get

263 ms

pixel

pixel

231 ms

chatplusscript.min.js

chatplusscript.min.js

178 ms

jqueryc.min.js

jqueryc.min.js

61 ms

riot%2Bcompiler_2.min.js

riot%2Bcompiler_2.min.js

62 ms

underscorec.min.js

underscorec.min.js

62 ms

c

c

461 ms

iframe

iframe

198 ms

Pug

Pug

102 ms

hs

hs

855 ms

sync.ad-stir.com

sync.ad-stir.com

856 ms

tap.php

tap.php

115 ms

sync

sync

1024 ms

113 ms

cookiesync

cookiesync

853 ms

cs

cs

854 ms

sync.ad

sync.ad

269 ms

cs

cs

853 ms

sync

sync

287 ms

sync

sync

112 ms

e8a805c6_2

e8a805c6_2

202 ms

pixel

pixel

17 ms

bounce

bounce

11 ms

sd

sd

9 ms

google

google

167 ms

sync

sync

17 ms

all-cp.min.css

all-cp.min.css

5 ms

chat_common.min.css

chat_common.min.css

170 ms

chat.min.css

chat.min.css

333 ms

design.1711924412.css

design.1711924412.css

10 ms

custom.1591948527.css

custom.1591948527.css

11 ms

onerror.min.js

onerror.min.js

567 ms

visitor-client.min.js

visitor-client.min.js

704 ms

slick.min.js

slick.min.js

9 ms

startup

startup

566 ms

Accessibility Review

guppy.jp accessibility score

91

Accessibility Issues

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

Buttons do not have an accessible name

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.

Best Practices

guppy.jp best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

guppy.jp SEO score

96

Search Engine Optimization Advices

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

guppy.jp

Open Graph data is detected on the main page of Guppy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: