1242.com website review

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

45 images could be 5.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, ptengine.jp and STINGRAY and others), adding 1.9 MB and 620 ms of main-thread time.

About 388 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

Google Tag Manager costs a phone 439 ms of main-thread work and 772 KiB 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.

Google Fonts costs a phone 1 ms of main-thread work and 987 KiB 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.

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

About 30 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

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.

3 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “前の 番組 放送時間25:00 ～ 27:00 霜降り明星のオールナイトニッポン パーソナリティ：霜降り明星(せいや/…”.

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

The layout shifts by 0.27 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Real visitors wait 939 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.6 MB in 218 requests on a phone: images 6.6 MB (91), scripts 1.0 MB (28) and fonts 957 KiB (44). Under 2 MB keeps phones on slow connections fast.

banner_v2.png weighs 1.2 MB. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example banner_v2.png at 2,160 px wide, shown at 178 px. Resized copies would save about 1.7 MB.

40 images (5.9 MB) 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.

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

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

Links must have discernible text: 12 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

1 element hidden from screen readers can still receive keyboard focus.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Your title is only 21 characters: “ニッポン放送 ラジオAM1242+FM93”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your <h1> is empty.

The homepage links to 47 pages on 1242.com and 71 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/timetable and /personality use the same meta description. A description written for each page earns more clicks.

/lf_bousai, /toku, /love, /akko, /sandradioshow and /sm and 4 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.

/lf_bousai, /toku, /love, /akko, /sandradioshow and /sm and 3 others took over 3 s to send their HTML from our server.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

1242.com 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.

1242.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 11 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 232 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

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 Ads, Google Analytics, Google Tag Manager and The Trade Desk (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 17 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.