Oen.tw Site Title

應援科技:為意義尋找資源、為資源尋找意義

Oen.tw Meta Description

以「經營認同」為導向的新世代募款工具,協助組織處理「支持者關係」而非交易形式的金流服務

Oen.tw Test Results

Oen.tw Mobile Performance: 28/100
Quick overview:
Max Potential First Input Delay
520 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
8.1 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.
First Meaningful Paint
2.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 887 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.
Properly size images
Potential savings of 631 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Avoid large layout shifts
2 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused JavaScript
Potential savings of 80 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.
Minimize main-thread work
5.8 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 JavaScript execution time
2.7 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 initial server response time
Root document took 2,050 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.
Largest Contentful Paint element
9,980 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
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
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

Oen.tw Mobile SEO: 100/100
Quick overview:

Oen.tw Mobile Best Practices: 83/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 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.
Oen.tw Mobile Accessibility: 83/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.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
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 tests
www.oen.com
www.oen.net
www.oen.org
www.oen.info
www.oen.biz
www.oen.us
www.oen.mobi
www.en.tw
www.oen.tw
www.ien.tw
www.oien.tw
www.ioen.tw
www.ken.tw
www.oken.tw
www.koen.tw
www.len.tw
www.olen.tw
www.loen.tw
www.pen.tw
www.open.tw
www.poen.tw
www.on.tw
www.own.tw
www.oewn.tw
www.owen.tw
www.osn.tw
www.oesn.tw
www.osen.tw
www.odn.tw
www.oedn.tw
www.oden.tw
www.orn.tw
www.oern.tw
www.oren.tw
www.oe.tw
www.oeb.tw
www.oenb.tw
www.oebn.tw
www.oeh.tw
www.oenh.tw
www.oehn.tw
www.oej.tw
www.oenj.tw
www.oejn.tw
www.oem.tw
www.oenm.tw
www.oemn.tw
Last Tested: