https://moica.nat.gov.tw/index.html
64
Performance
74
Accessibility
67
Best Practices
70
SEO
PWA
64
Performance
74
Accessibility
67
Best Practices
70
SEO
PWA
64
Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
2.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Time to Interactive
3.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index
2.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time
150 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Largest Contentful Paint
3.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Cumulative Layout Shift
0.006
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Opportunities
Opportunity
Estimated Savings
Eliminate render-blocking resources
1.31 s
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.FCPLCP
URL
Transfer Size
Potential Savings
/css/jquery.mmenu.css
(moica.nat.gov.tw)
55.0 KiB
530 ms
/css/swiper.min.css
(moica.nat.gov.tw)
13.6 KiB
530 ms
/css/global.css
(moica.nat.gov.tw)
12.9 KiB
530 ms
/css/mmenu.css
(moica.nat.gov.tw)
2.6 KiB
530 ms
/css/index.css
(moica.nat.gov.tw)
4.8 KiB
530 ms
/js/jquery-3.4.1.min.js
(moica.nat.gov.tw)
85.7 KiB
880 ms
/js/jquery.mmenu.js
(moica.nat.gov.tw)
23.7 KiB
700 ms
/js/swiper.min.js
(moica.nat.gov.tw)
136.1 KiB
1,050 ms
/js/main.js
(moica.nat.gov.tw)
0.8 KiB
530 ms
/js/index.js
(moica.nat.gov.tw)
1.6 KiB
530 ms
/js/chat.js
(moica.nat.gov.tw)
1.5 KiB
180 ms
/js/AC_RunActiveContent.js
(moica.nat.gov.tw)
8.4 KiB
180 ms
Use HTTP/2
0.89 s
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
URL
Protocol
/index.html
(moica.nat.gov.tw)
http/1.1
/css/jquery.mmenu.css
(moica.nat.gov.tw)
http/1.1
/css/swiper.min.css
(moica.nat.gov.tw)
http/1.1
/css/global.css
(moica.nat.gov.tw)
http/1.1
/css/mmenu.css
(moica.nat.gov.tw)
http/1.1
/js/jquery-3.4.1.min.js
(moica.nat.gov.tw)
http/1.1
/js/jquery.mmenu.js
(moica.nat.gov.tw)
http/1.1
/js/swiper.min.js
(moica.nat.gov.tw)
http/1.1
/js/main.js
(moica.nat.gov.tw)
http/1.1
/css/index.css
(moica.nat.gov.tw)
http/1.1
/js/index.js
(moica.nat.gov.tw)
http/1.1
/js/chat.js
(moica.nat.gov.tw)
http/1.1
/js/AC_RunActiveContent.js
(moica.nat.gov.tw)
http/1.1
/images/h1.png
(moica.nat.gov.tw)
http/1.1
/images/icon-fb.svg
(moica.nat.gov.tw)
http/1.1
…leftBanner/1587064….jpg
(moica.nat.gov.tw)
http/1.1
/images/ico-qrcode.svg
(moica.nat.gov.tw)
http/1.1
/images/tag-1A.png
(moica.nat.gov.tw)
http/1.1
/images/icon-search.svg
(moica.nat.gov.tw)
http/1.1
/images/icon-nav01.svg
(moica.nat.gov.tw)
http/1.1
/images/icon-nav02.svg
(moica.nat.gov.tw)
http/1.1
/images/icon-nav03.svg
(moica.nat.gov.tw)
http/1.1
/images/icon-nav04.svg
(moica.nat.gov.tw)
http/1.1
/images/icon-nav05.svg
(moica.nat.gov.tw)
http/1.1
/images/icon-nav06.svg
(moica.nat.gov.tw)
http/1.1
/images/icon-nav07.svg
(moica.nat.gov.tw)
http/1.1
/images/view-ind.jpg
(moica.nat.gov.tw)
http/1.1
/images/tag-hot.svg
(moica.nat.gov.tw)
http/1.1
/images/icon-fb-wh.svg
(moica.nat.gov.tw)
http/1.1
/images/ico-ft-phone.svg
(moica.nat.gov.tw)
http/1.1
/images/ico-ft-clock.svg
(moica.nat.gov.tw)
http/1.1
/moica/viewCount.do
(moica.nat.gov.tw)
http/1.1
/images/chat-meili.png
(moica.nat.gov.tw)
http/1.1
Enable text compression
0.69 s
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.FCPLCP
URL
Transfer Size
Potential Savings
/js/swiper.min.js
(moica.nat.gov.tw)
135.8 KiB
101.2 KiB
/js/jquery-3.4.1.min.js
(moica.nat.gov.tw)
85.4 KiB
55.7 KiB
/css/jquery.mmenu.css
(moica.nat.gov.tw)
54.7 KiB
47.3 KiB
/index.html
(moica.nat.gov.tw)
23.3 KiB
17.6 KiB
/js/jquery.mmenu.js
(moica.nat.gov.tw)
23.4 KiB
16.8 KiB
/css/global.css
(moica.nat.gov.tw)
12.6 KiB
9.5 KiB
/css/swiper.min.css
(moica.nat.gov.tw)
13.3 KiB
9.3 KiB
/js/AC_RunActiveContent.js
(moica.nat.gov.tw)
8.1 KiB
5.8 KiB
/css/index.css
(moica.nat.gov.tw)
4.5 KiB
3.1 KiB
/css/mmenu.css
(moica.nat.gov.tw)
2.3 KiB
1.6 KiB
Reduce unused CSS
0.41 s
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.FCPLCP
URL
Transfer Size
Potential Savings
/earlyaccess/notosanstc.css
(fonts.googleapis.com)
293.5 KiB
293.5 KiB
/css/jquery.mmenu.css
(moica.nat.gov.tw)
55.0 KiB
52.8 KiB
/css/swiper.min.css
(moica.nat.gov.tw)
13.6 KiB
13.6 KiB
Reduce unused JavaScript
0.35 s
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.LCP
URL
Transfer Size
Potential Savings
/js/swiper.min.js
(moica.nat.gov.tw)
136.1 KiB
118.1 KiB
/js/jquery-3.4.1.min.js
(moica.nat.gov.tw)
85.7 KiB
37.7 KiB
Serve images in next-gen formats
0.2 s
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
URL
Resource Size
Potential Savings
139,063,198
<div class="view">
/images/view-ind.jpg
(moica.nat.gov.tw)
265.1 KiB
225.3 KiB
自然人憑證申請事項
<img src="/moica//upload/leftBanner/15870641a16000001640.jpg" alt="自然人憑證申請事項">
…leftBanner/1587064….jpg
(moica.nat.gov.tw)
42.6 KiB
34.3 KiB
MOICA內政部憑證管理中心
<img src="images/h1.png" alt="MOICA內政部憑證管理中心">
/images/h1.png
(moica.nat.gov.tw)
46.7 KiB
33.3 KiB
通過A檢測等級無障礙網頁檢測
<img src="images/tag-1A.png" width="512" height="180" aria-label="通過A檢測等級無障礙網頁檢測" alt="通過A檢測等級無障礙網頁檢測">
/images/tag-1A.png
(moica.nat.gov.tw)
35.7 KiB
25.3 KiB
Efficiently encode images
0.16 s
Optimized images load faster and consume less cellular data. Learn more.
URL
Resource Size
Potential Savings
139,063,198
<div class="view">
/images/view-ind.jpg
(moica.nat.gov.tw)
265.1 KiB
173.8 KiB
自然人憑證申請事項
<img src="/moica//upload/leftBanner/15870641a16000001640.jpg" alt="自然人憑證申請事項">
…leftBanner/1587064….jpg
(moica.nat.gov.tw)
42.6 KiB
26.0 KiB
These suggestions can help your page load faster. They don't directly affect the Performance score.
Diagnostics
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.FCPLCP
URL
Potential Savings
…v35/-nF7OG829….115.woff2
(fonts.gstatic.com)
70 ms
…v35/-nF7OG829….119.woff2
(fonts.gstatic.com)
60 ms
…v35/-nF7OG829….118.woff2
(fonts.gstatic.com)
90 ms
…v35/-nF7OG829….117.woff2
(fonts.gstatic.com)
90 ms
…v35/-nF7OG829….110.woff2
(fonts.gstatic.com)
90 ms
…v35/-nF7OG829….116.woff2
(fonts.gstatic.com)
90 ms
…v35/-nF7OG829….113.woff2
(fonts.gstatic.com)
90 ms
…v35/-nF7OG829….114.woff2
(fonts.gstatic.com)
90 ms
…v35/-nF7OG829….112.woff2
(fonts.gstatic.com)
90 ms
…v35/-nF7OG829….107.woff2
(fonts.gstatic.com)
90 ms
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.
Source
/js/jquery-3.4.1.min.js:2:38438
(moica.nat.gov.tw)
Avoid chaining critical requests 21 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.FCPLCP
Maximum critical path latency: 1,940 ms
Initial Navigation
/index.html
(moica.nat.gov.tw)
/css/jquery.mmenu.css
(moica.nat.gov.tw)
- 410 ms, 54.98 KiB
/css/swiper.min.css
(moica.nat.gov.tw)
- 430 ms, 13.62 KiB
/css/global.css
(moica.nat.gov.tw)
/earlyaccess/notosanstc.css
(fonts.googleapis.com)
…v35/-nF7OG829….115.woff2
(fonts.gstatic.com)
- 70 ms, 72.38 KiB
…v35/-nF7OG829….119.woff2
(fonts.gstatic.com)
- 60 ms, 35.39 KiB
…v35/-nF7OG829….118.woff2
(fonts.gstatic.com)
- 90 ms, 58.94 KiB
…v35/-nF7OG829….117.woff2
(fonts.gstatic.com)
- 90 ms, 65.15 KiB
…v35/-nF7OG829….110.woff2
(fonts.gstatic.com)
- 90 ms, 75.93 KiB
…v35/-nF7OG829….116.woff2
(fonts.gstatic.com)
- 90 ms, 70.18 KiB
…v35/-nF7OG829….113.woff2
(fonts.gstatic.com)
- 90 ms, 71.27 KiB
…v35/-nF7OG829….114.woff2
(fonts.gstatic.com)
- 90 ms, 70.44 KiB
…v35/-nF7OG829….112.woff2
(fonts.gstatic.com)
- 90 ms, 72.76 KiB
…v35/-nF7OG829….107.woff2
(fonts.gstatic.com)
- 90 ms, 70.77 KiB
/css/mmenu.css
(moica.nat.gov.tw)
- 430 ms, 2.58 KiB
/css/index.css
(moica.nat.gov.tw)
- 430 ms, 4.80 KiB
/js/jquery-3.4.1.min.js
(moica.nat.gov.tw)
- 840 ms, 85.71 KiB
/js/jquery.mmenu.js
(moica.nat.gov.tw)
- 560 ms, 23.70 KiB
/js/swiper.min.js
(moica.nat.gov.tw)
- 1,000 ms, 136.09 KiB
/js/main.js
(moica.nat.gov.tw)
- 580 ms, 0.81 KiB
/js/index.js
(moica.nat.gov.tw)
- 580 ms, 1.61 KiB
/js/chat.js
(moica.nat.gov.tw)
- 580 ms, 1.47 KiB
/js/AC_RunActiveContent.js
(moica.nat.gov.tw)
- 710 ms, 8.42 KiB
Keep request counts low and transfer sizes small 44 requests • 1,740 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Resource Type
Requests
Transfer Size
Total
44
1,739.7 KiB
Font
10
663.2 KiB
Image
19
412.6 KiB
Stylesheet
6
382.4 KiB
Script
7
257.8 KiB
Document
1
23.6 KiB
Other
1
0.2 KiB
Media
0
0.0 KiB
Third-party
11
956.7 KiB
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element
139,063,198
<div class="view">
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.CLS
Element
CLS Contribution
關於MOICA
<li>
0.002
資訊公開
<li>
0.001
憑證作業
<li>
0.001
公告訊息
<li>
0.001
儲存庫
<li>
0.001
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn moreTBT
URL
Start Time
Duration
/js/jquery-3.4.1.min.js
(moica.nat.gov.tw)
2,068 ms
200 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (26)
Show Hide
Properly size images Potential savings of 68 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
URL
Resource Size
Potential Savings
MOICA內政部憑證管理中心
<img src="images/h1.png" alt="MOICA內政部憑證管理中心">
/images/h1.png
(moica.nat.gov.tw)
46.7 KiB
35.2 KiB
通過A檢測等級無障礙網頁檢測
<img src="images/tag-1A.png" width="512" height="180" aria-label="通過A檢測等級無障礙網頁檢測" alt="通過A檢測等級無障礙網頁檢測">
/images/tag-1A.png
(moica.nat.gov.tw)
35.7 KiB
33.3 KiB
Defer offscreen images Potential savings of 47 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
URL
Resource Size
Potential Savings
自然人憑證申請事項
<img src="/moica//upload/leftBanner/15870641a16000001640.jpg" alt="自然人憑證申請事項" width="650" height="638">
…leftBanner/1587064….jpg
(moica.nat.gov.tw)
42.6 KiB
42.6 KiB
QR Code
<img src="images/ico-qrcode.svg" alt="QR Code">
/images/ico-qrcode.svg
(moica.nat.gov.tw)
4.0 KiB
4.0 KiB
Minify CSS Potential savings of 35 KiB
Minifying CSS files can reduce network payload sizes. Learn more.FCPLCP
URL
Transfer Size
Potential Savings
/earlyaccess/notosanstc.css
(fonts.googleapis.com)
293.5 KiB
32.8 KiB
/css/global.css
(moica.nat.gov.tw)
12.9 KiB
2.3 KiB
Minify JavaScript Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.FCPLCP
URL
Transfer Size
Potential Savings
/js/AC_RunActiveContent.js
(moica.nat.gov.tw)
8.4 KiB
3.0 KiB
Preconnect to required origins Potential savings of 90 ms
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.FCPLCP
URL
Potential Savings
https://fonts.gstatic.com
90 ms
https://fonts.googleapis.com
80 ms
Initial server response time was short Root document took 150 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.FCPLCP
URL
Time Spent
/index.html
(moica.nat.gov.tw)
150 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.FCPLCP
Preload key requests
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.FCPLCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn moreLCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. TBT
Avoid serving legacy JavaScript to modern browsers
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 MoreTBT
Preload Largest Contentful Paint image Potential savings of 10 ms
Preload the image used by the LCP element in order to improve your LCP time. Learn more.LCP
URL
Potential Savings
139,063,198
<div class="view">
/images/view-ind.jpg
(moica.nat.gov.tw)
10 ms
Avoids enormous network payloads Total size was 1,740 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.LCP
URL
Transfer Size
/earlyaccess/notosanstc.css
(fonts.googleapis.com)
293.5 KiB
/images/view-ind.jpg
(moica.nat.gov.tw)
265.4 KiB
/js/swiper.min.js
(moica.nat.gov.tw)
136.1 KiB
/js/jquery-3.4.1.min.js
(moica.nat.gov.tw)
85.7 KiB
…v35/-nF7OG829….110.woff2
(fonts.gstatic.com)
75.9 KiB
…v35/-nF7OG829….112.woff2
(fonts.gstatic.com)
72.8 KiB
…v35/-nF7OG829….115.woff2
(fonts.gstatic.com)
72.4 KiB
…v35/-nF7OG829….113.woff2
(fonts.gstatic.com)
71.3 KiB
…v35/-nF7OG829….107.woff2
(fonts.gstatic.com)
70.8 KiB
…v35/-nF7OG829….114.woff2
(fonts.gstatic.com)
70.4 KiB
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoids an excessive DOM size 232 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.TBT
Statistic
Element
Value
Total DOM Elements
232
Maximum DOM Depth
內政部粉絲專頁
<img src="images/icon-fb.svg" alt="內政部粉絲專頁">
9
Maximum Child Elements
關鍵字搜尋 …
<ul class="mm-listview">
12
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
/js/jquery-3.4.1.min.js
(moica.nat.gov.tw)
259 ms
252 ms
2 ms
/index.html
(moica.nat.gov.tw)
167 ms
3 ms
1 ms
Unattributable
123 ms
2 ms
0 ms
Minimizes main-thread work 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn moreTBT
Category
Time Spent
Script Evaluation
261 ms
Other
157 ms
Style & Layout
123 ms
Parse HTML & CSS
22 ms
Rendering
10 ms
Script Parsing & Compilation
6 ms
Minimize third-party usage Third-party code blocked the main thread for 0 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.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Fonts
957 KiB
0 ms
/earlyaccess/notosanstc.css
(fonts.googleapis.com)
294 KiB
0 ms
…v35/-nF7OG829….110.woff2
(fonts.gstatic.com)
76 KiB
0 ms
…v35/-nF7OG829….112.woff2
(fonts.gstatic.com)
73 KiB
0 ms
…v35/-nF7OG829….115.woff2
(fonts.gstatic.com)
72 KiB
0 ms
…v35/-nF7OG829….113.woff2
(fonts.gstatic.com)
71 KiB
0 ms
Other resources
371 KiB
0 ms
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more.
Element
139,063,198
<div class="view">
Avoids document.write()
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn moreCLS
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn moreCLS
Has a <meta name="viewport"> tag with width or initial-scale
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Avoids unload event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
74
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.
ARIA
ARIA IDs are not unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
Failing Elements
ul.mm-listview > form.mm-listitem > li > input#keyword
<input id="keyword" name="keyword" type="text" placeholder="關鍵字搜尋">
ul.topGuid > form > li > input#keyword
<input id="keyword" name="keyword" type="text" accesskey="4" placeholder="關鍵字搜尋">
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.
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.
Failing Elements
head > meta
<meta name="viewport" content="width=device-width,initial-scale=1, user-scalable=no">
These items highlight common accessibility best practices.
Contrast
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.
Failing Elements
送出關鍵字
<input type="submit" aria-label="送出關鍵字" value="GO">
Commonly used functions
<span>
常用功能 Commonly used functions
<h2 alt="常用功能">
十大常見問題
<span style="color: orange">
十大常見問題
<a href="tenMajorFaq.html">
Latest News
<span>
最新消息Latest News more 2023-08-21 112年「使用行動自然人憑證，破萬好禮送給你！」中獎名單公布 2022-02-16 行動自然人…
<div class="news" aria-label="最新消息區塊">
more
<span aria-hidden="true">
最新消息Latest News more 2023-08-21 112年「使用行動自然人憑證，破萬好禮送給你！」中獎名單公布 2022-02-16 行動自然人…
<div class="news" aria-label="最新消息區塊">
These are opportunities to improve the legibility of your content.
Tables and lists
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.
Failing Elements
跳到右上方功能區 English 網站導覽 關鍵字搜尋
<ul class="topGuid">
關鍵字搜尋
<form method="post" action="/moica/search.do">
List items (<li>) are not contained within <ul> or <ol> parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
Failing Elements
關鍵字搜尋
<li>
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Additional items to manually check (10)
Show Hide
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (14)
Show Hide
[aria-*] attributes match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn more.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
<html> element has 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.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Links 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 more.
Heading elements appear 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.
Not applicable (25)
Show Hide
button, link, and menuitem elements 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 more.
ARIA input fields have accessible names
When an input field 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 more.
ARIA meter elements 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 more.
ARIA progressbar elements have accessible names
When a `progressbar` 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 more.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
ARIA toggle fields have accessible names
When a toggle field 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 more.
ARIA tooltip elements 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 more.
ARIA treeitem elements 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 more.
Buttons 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 more.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Definition list items are wrapped in <dl> elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.
[id] attributes on active, focusable elements are unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn more.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
<input type="image"> elements have [alt] text
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more.
No element has 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.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
67
Best Practices
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
URL
Aspect Ratio (Displayed)
Aspect Ratio (Actual)
自然人憑證申請事項
<img src="/moica//upload/leftBanner/15870641a16000001640.jpg" alt="自然人憑證申請事項" width="650" height="638">
…leftBanner/1587064….jpg
(moica.nat.gov.tw)
650 x 638 (1.02)
250 x 145 (1.72)
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Expected publicId to be an empty string
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
General
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more.
Deprecation / Warning
Source
Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/.
/js/jquery-3.4.1.min.js:2:79716
(moica.nat.gov.tw)
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
Source
Description
/index.html:153:0
(moica.nat.gov.tw)
SyntaxError: Unexpected end of input
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name
Version
jQuery
3.7.0
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Description
Directive
Severity
No CSP found in enforcement mode
High
Passed audits (9)
Show Hide
Uses HTTPS
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.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.
Avoids front-end JavaScript libraries with known security vulnerabilities
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more.
No issues in the Issues panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
URL
Map URL
/js/swiper.min.js
(moica.nat.gov.tw)
/js/swiper.min.js.map
(moica.nat.gov.tw)
Error: Failed fetching source map (404)
Not applicable (1)
Show Hide
Fonts with font-display: optional are preloaded
Preload `optional` fonts so first-time visitors may use them. Learn more
70
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more.
Content Best Practices
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content. Learn more.
Link destination
Link Text
/news_1.html
(moica.nat.gov.tw)
more
Format your HTML in a way that enables crawlers to better understand your app’s content.
Crawling and Indexing
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
Uncrawlable Link
Menu
<a class="mm-navbar__title">
To appear in search results, crawlers need access to your app.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (7)
Show Hide
Has a <meta name="viewport"> tag with width or initial-scale
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
Image elements 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 has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
Not applicable (4)
Show Hide
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more.
Tap targets are sized appropriately
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
PWA
These checks validate the aspects of a Progressive Web App. Learn more.
Installable
Web app manifest or service worker do not meet the installability requirements 1 reason
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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Failure reason
No manifest was fetched
PWA Optimized
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.
Is not configured for a custom splash screen
Failures: No manifest was fetched.
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more.
Does not set a theme color for the address bar.
Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
The browser address bar can be themed to match your site. Learn more.
Content is sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.
Has a <meta name="viewport"> tag with width or initial-scale
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Does not provide a valid apple-touch-icon
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Manifest doesn't have a maskable icon
No manifest was fetched
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.
Additional items to manually check (3)
Show Hide
Site works cross-browser
To reach the most number of users, sites should work across every major browser. Learn more.
Page transitions don't feel like they block on the network
Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more.
Each page has a URL
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more.
These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.