Port17.net Site Title

迷走ノンプログラマーの独り言

Port17.net Meta Description

勉強の為色んな書籍を書い、損したり得したり、そしてわからない時は色んなサイトの管理者様やコメントに助けて頂きました。私もそんなサイトを目指せればと思い作成しました。ぜひ皆様のお力になれるようなサイトになれるように頑張ります。

Port17.net Test Results

Port17.net Mobile Performance: 58/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce initial server response time
Root document took 1,810 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.
Eliminate render-blocking resources
Potential savings of 1,530 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.
Largest Contentful Paint element
2,590 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Potential savings of 179 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.
Reduce JavaScript execution time
7.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Reduce the impact of third-party code
Third-party code blocked the main thread for 3,250 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.
Reduce unused CSS
Potential savings of 28 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Minimize main-thread work
7.6 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
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.
Serve static assets with an efficient cache policy
23 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Minify JavaScript
Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 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
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`.
Max Potential First Input Delay
3,190 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.
Time to Interactive
6.9 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.

Port17.net Mobile SEO: 100/100
Quick overview:

Port17.net Mobile Best Practices: 59/100
Quick overview:
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 about this errors in console diagnostic audit
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
35 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.
Port17.net Mobile Accessibility: 75/100
Quick overview:
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.
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.
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.
Similar sites
Similar tests
www.port17.com
www.port17.net
www.port17.org
www.port17.info
www.port17.biz
www.port17.us
www.port17.mobi
www.ort17.net
www.port17.net
www.oort17.net
www.poort17.net
www.oport17.net
www.lort17.net
www.plort17.net
www.lport17.net
www.prt17.net
www.pirt17.net
www.poirt17.net
www.piort17.net
www.pkrt17.net
www.pokrt17.net
www.pkort17.net
www.plrt17.net
www.polrt17.net
www.pprt17.net
www.poprt17.net
www.pport17.net
www.pot17.net
www.poet17.net
www.poret17.net
www.poert17.net
www.podt17.net
www.pordt17.net
www.podrt17.net
www.poft17.net
www.porft17.net
www.pofrt17.net
www.pott17.net
www.portt17.net
www.potrt17.net
www.por17.net
www.porr17.net
www.portr17.net
www.porrt17.net
www.porf17.net
www.portf17.net
www.porg17.net
www.portg17.net
www.porgt17.net
www.pory17.net
www.porty17.net
www.poryt17.net
www.port7.net
www.port1.net
Last Tested: