skillty.jp website review

16 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.9 s.

70 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

About 421 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.

13 images could be 709 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

4 third-party services load with your homepage (Google Tag Manager, Clarity and Google Fonts and others), adding 2.8 MB and 183 ms of main-thread time.

43 KiB could be saved by minifying CSS.

Google Fonts costs a phone 17 ms of main-thread work and 2.6 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

5 long tasks block the main thread while loading, the longest for 184 ms. During a long task the page ignores taps.

About 73 KiB of JavaScript is downloaded but never used on this page.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “育てても辞めず、 稼げる会社へ。”.

Visually, the page fills in at 12.0 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 17.5 s. Good is under 3.8 s.

The first text or image appears after 4.5 s on a phone. Good is under 1.8 s.

7 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 4.4 MB in 226 requests on a phone: fonts 2.2 MB (173), images 1.5 MB (24) and stylesheets 450 KiB (16). Under 2 MB keeps phones on slow connections fast.

5 images (624 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

4 images are downloaded at several times the size a phone draws them, for example hero_pc.png at 1,200 px wide, shown at 276 px. Resized copies would save about 419 KiB.

3 images further down the page (151 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 149.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 56 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

The homepage links to 65 pages on skillty.jp and 52 external pages.

/company.php, /contact.php, /check, /category/news, /article/news-aisummit-revival-2026 and /article/news-book-claude-tankobon and 5 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/check, /category/news, /article/news-aisummit-revival-2026, /article/news-book-claude-tankobon, /replay.php and /services.php took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link to other sites is dead, for example https://link.amazon/B09J7kvW4 (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

skillty.jp has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 299 words of visible text.

DMARC is set to p=none, so mail pretending to be skillty.jp is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 5 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.