Fedelat.info Site Title

Fedelat Edit | テニス好きのへぼプランナーが綴る、奇妙に微妙なブログ。貴方のスキマ時間を2分間だけ暇つぶしできます！　アクセスしてくれた人に潤いと幸運と良い1日を！

Fedelat.info Meta Description

テニス好きのへぼプランナーが綴る、奇妙に微妙なブログ。貴方のスキマ時間を2分間だけ暇つぶしできます！　アクセスしてくれた人に潤いと幸運と良い1日を！

Fedelat.info Test Results

Fedelat.info Mobile Performance: 49/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
4.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Reduce the impact of third-party code
Third-party code blocked the main thread for 290 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 how to minimize third-party impact.
Eliminate render-blocking resources
Potential savings of 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 how to eliminate render-blocking resources.
Reduce initial server response time
Root document took 830 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Efficiently encode images
Potential savings of 578 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Properly size images
Potential savings of 56 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce unused JavaScript
Potential savings of 235 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Serve images in next-gen formats
Potential savings of 799 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Enable text compression
Potential savings of 106 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Largest Contentful Paint element
10,280 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
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 about `font-display`.
Serve static assets with an efficient cache policy
36 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 21 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Minify JavaScript
Potential savings of 4 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Time to Interactive
12.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Fedelat.info Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Fedelat.info Mobile Best Practices: 59/100
Quick overview:
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Trust and Safety
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Does not use HTTPS
29 insecure requests 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 served over 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 about HTTPS.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Fedelat.info Mobile Accessibility: 76/100
Quick overview:
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 how to provide sufficient color contrast.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`button`, `link`, and `menuitem` elements do not have accessible names.
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
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 about the viewport meta tag.
Similar sites
Similar tests
www.fedelat.com
www.fedelat.net
www.fedelat.org
www.fedelat.info
www.fedelat.biz
www.fedelat.us
www.fedelat.mobi
www.edelat.info
www.fedelat.info
www.cedelat.info
www.fcedelat.info
www.cfedelat.info
www.dedelat.info
www.fdedelat.info
www.dfedelat.info
www.redelat.info
www.fredelat.info
www.rfedelat.info
www.tedelat.info
www.ftedelat.info
www.tfedelat.info
www.gedelat.info
www.fgedelat.info
www.gfedelat.info
www.vedelat.info
www.fvedelat.info
www.vfedelat.info
www.fdelat.info
www.fwdelat.info
www.fewdelat.info
www.fwedelat.info
www.fsdelat.info
www.fesdelat.info
www.fsedelat.info
www.fddelat.info
www.feddelat.info
www.frdelat.info
www.ferdelat.info
www.feelat.info
www.fexelat.info
www.fedxelat.info
www.fexdelat.info
www.feselat.info
www.fedselat.info
www.feeelat.info
www.fedeelat.info
www.feedelat.info
www.ferelat.info
www.fedrelat.info
www.fefelat.info
www.fedfelat.info
www.fefdelat.info
www.fecelat.info
www.fedcelat.info
www.fecdelat.info
www.fedlat.info
www.fedwlat.info
www.fedewlat.info
www.fedwelat.info
www.fedslat.info
www.fedeslat.info
www.feddlat.info
www.fededlat.info
www.fedrlat.info
www.federlat.info
www.fedeat.info
www.fedepat.info
www.fedelpat.info
www.fedeplat.info
www.fedeoat.info
www.fedeloat.info
www.fedeolat.info
www.fedekat.info
www.fedelkat.info
www.fedeklat.info
www.fedelt.info
www.fedelqt.info
www.fedelaqt.info
www.fedelqat.info
www.fedelwt.info
www.fedelawt.info
www.fedelwat.info
www.fedelst.info
www.fedelast.info
www.fedelsat.info
www.fedelzt.info
www.fedelazt.info
www.fedelzat.info
www.fedela.info
www.fedelar.info
www.fedelatr.info
www.fedelart.info
www.fedelaf.info
www.fedelatf.info
www.fedelaft.info
www.fedelag.info
www.fedelatg.info
www.fedelagt.info
www.fedelay.info
www.fedelaty.info
www.fedelayt.info
Last Tested: