Tenki.jp Site Title

日本気象協会 tenki.jp【公式】 / 天気・地震・台風

Tenki.jp Meta Description

日本気象協会公式の天気予報専門メディアです。市区町村別のピンポイントな天気予報に加え、専門的な気象情報、地震・津波などの防災情報を提供します。気象予報士が日々更新する日直予報士、花粉や熱中症、スキー積雪などの季節特集も人気です。

Tenki.jp Test Results

Tenki.jp Mobile Performance: 18/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats. Potential savings of 1,027 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Efficiently encode images. Potential savings of 725 KiB
Optimized images load faster and consume less cellular data. Learn more.
Properly size images. Potential savings of 455 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Remove unused JavaScript. Potential savings of 450 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Eliminate render-blocking resources. Potential savings of 1,300 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Avoid multiple page redirects. Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Defer offscreen images. Potential savings of 147 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Enable text compression. Potential savings of 56 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
16.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,150 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Serve static assets with an efficient cache policy
109 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Reduce JavaScript execution time
9.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid enormous network payloads
Total size was 4,028 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid an excessive DOM size
1,009 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid large layout shifts
3 elements found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
User Timing marks and measures
14 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Keep request counts low and transfer sizes small
530 requests • 4,028 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
8 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Tenki.jp Mobile SEO: 77/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Document does not have a valid `rel=canonical`
Canonical links suggest which URL to show in search results. Learn more. Points to the domain's root URL (the homepage), instead of an equivalent page of content
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More

Tenki.jp Mobile Best Practices: 62/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Includes front-end JavaScript libraries with known security vulnerabilities
3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Tenki.jp Mobile Progressive Web App: 25/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Installable
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Page load is not fast enough on mobile networks
Interactive at 34.7 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
Tenki.jp Mobile Accessibility: 53/100
Quick overview:
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
Tables and lists
These are opportunities to to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
Similar tests
www.tenki.com
www.tenki.net
www.tenki.org
www.tenki.info
www.tenki.biz
www.tenki.us
www.tenki.mobi
www.enki.jp
www.tenki.jp
www.renki.jp
www.trenki.jp
www.rtenki.jp
www.fenki.jp
www.tfenki.jp
www.ftenki.jp
www.genki.jp
www.tgenki.jp
www.gtenki.jp
www.yenki.jp
www.tyenki.jp
www.ytenki.jp
www.tnki.jp
www.twnki.jp
www.tewnki.jp
www.twenki.jp
www.tsnki.jp
www.tesnki.jp
www.tsenki.jp
www.tdnki.jp
www.tednki.jp
www.tdenki.jp
www.trnki.jp
www.ternki.jp
www.teki.jp
www.tebki.jp
www.tenbki.jp
www.tebnki.jp
www.tehki.jp
www.tenhki.jp
www.tehnki.jp
www.tejki.jp
www.tenjki.jp
www.tejnki.jp
www.temki.jp
www.tenmki.jp
www.temnki.jp
www.teni.jp
www.tenji.jp
www.tenkji.jp
www.tenii.jp
www.tenkii.jp
www.teniki.jp
www.tenmi.jp
www.tenkmi.jp
www.tenli.jp
www.tenkli.jp
www.tenlki.jp
www.tenoi.jp
www.tenkoi.jp
www.tenoki.jp
www.tenk.jp
www.tenku.jp
www.tenkiu.jp
www.tenkui.jp
www.tenkj.jp
www.tenkij.jp
www.tenkk.jp
www.tenkik.jp
www.tenkki.jp
www.tenko.jp
www.tenkio.jp
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.