Storm.mg 風傳媒 | Storm.mg
風傳媒擁有首屈一指、最強大、最優秀的編輯團隊及記者群，以最宏觀的視野掌握國際、國內的新聞、政治、兩岸動態，提供最優秀的原生新聞，讓使用者能看見最公正、真實的新聞內容，並且在本站發表個人的想法與見的，讓全世界都能聽見風傳媒網站中每一位會員的聲音。
storm.mg Desktop Performance
50/100
These metrics represent real-world Chrome users experience viewing storm.mg web page. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
Cumulative Layout Shift
First Input Delay
First Contentful Paint
Largest Contentful Paint
Metrics
Largest Contentful Paint1/100 8.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Time to Interactive26/100 6.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index40/100 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First Contentful Paint69/100 1.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Total Blocking Time98/100 90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift100/100 0.025
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (19)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Defer offscreen images
Potential savings of 2,152 KiB
1,870 ms
Properly size images
Potential savings of 1,873 KiB
1,610 ms
Serve images in next-gen formats
Potential savings of 1,151 KiB
950 ms
Eliminate render-blocking resources
Potential savings of 200 ms
200 ms
Remove unused JavaScript
Potential savings of 260 KiB
200 ms
Remove unused CSS
Potential savings of 160 KiB
160 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid `document.write()`
Ensure text remains visible during webfont load
Does not use passive listeners to improve scrolling performance
Avoid enormous network payloads
Total size was 7,776 KiB
Avoid an excessive DOM size
2,950 elements
Serve static assets with an efficient cache policy
38 resources found
Minimize main-thread work
3.9 s
JavaScript execution time
1.0 s
Avoid long main-thread tasks
8 long tasks found
Avoid chaining critical requests
93 chains found
Keep request counts low and transfer sizes small
300 requests • 7,776 KiB
Avoid large layout shifts
5 elements found
Largest Contentful Paint element
1 element found
Passed Audits (10)
Minify CSS
Potential savings of 11 KiB
Use video formats for animated content
Minify JavaScript
Preload key requests
Efficiently encode images
Enable text compression
Minimize third-party usage
Third-party code blocked the main thread for 10 ms
Avoid multiple page redirects
Potential savings of 190 ms
Preconnect to required origins
Initial server response time was short
Root document took 120 ms
storm.mg Desktop SEO
92/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (1)
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Passed Audits (11)
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid
Links have descriptive text
Page isn’t blocked from indexing
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Page has successful HTTP status code
Document avoids plugins
Image elements have `[alt]` attributes
Document has a `<title>` element
Document has a meta description
storm.mg Desktop Best Practices
69/100
These checks highlight opportunities to improve the overall code health of storm.mg page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (4)
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
9 vulnerabilities detected
Does not use HTTPS
1 insecure request found
Links to cross-origin destinations are unsafe
General
Browser errors were logged to the console
Passed Audits (10)
Avoids requesting the notification permission on page load
Page has the HTML doctype
Displays images with correct aspect ratio
Avoids Application Cache
Avoids requesting the geolocation permission on page load
Serves images with appropriate resolution
Avoids deprecated APIs
Allows users to paste into password fields
Properly defines charset
Detected JavaScript libraries
storm.mg Desktop Progressive Web App
19/100
These checks validate the aspects of a Progressive Web App. 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.
Should Fix (10)
PWA Optimized
Manifest doesn't have a maskable icon
Does not set a theme color for the address bar.
Is not configured for a custom splash screen
Does not provide a valid `apple-touch-icon`
Installable
Web app manifest does not meet the installability requirements
Does not register a service worker that controls page and `start_url`
Does not use HTTPS
1 insecure request found
Fast and reliable
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 31.9 s
`start_url` does not respond with a 200 when offline
Current page does not respond with a 200 when offline
Passed Audits (3)
Redirects HTTP traffic to HTTPS
Contains some content when JavaScript is not available
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
storm.mg Desktop Accessibility
84/100
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. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (4)
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.
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
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.
Passed Audits (21)
`[role]`s have all required `[aria-*]` attributes
`[aria-*]` attributes have valid values
ARIA IDs are unique
Heading elements appear in a sequentially-descending order
`[aria-hidden="true"]` elements do not contain focusable descendents
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
The page contains a heading, skip link, or landmark region
`[aria-*]` attributes are valid and not misspelled
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`<frame>` or `<iframe>` elements have a title
`[id]` attributes on active, focusable elements are unique
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
`[role]`s are contained by their required parent element
Buttons have an accessible name
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]` values are valid
`[aria-*]` attributes match their roles
Image elements have `[alt]` attributes
Document has a `<title>` element
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
Desktop Speed
44/100
These checks analyze the performance of storm.mg on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (5)
Optimize images
Leverage browser caching
Enable compression
Minify HTML
Minify JavaScript
Passed Audits (5)
Avoid landing page redirects
Reduce server response time
Minify CSS
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Prioritize visible content
www.storm.com
www.storm.net
www.storm.org
www.storm.info
www.storm.biz
www.storm.us
www.storm.mobi
www.torm.mg
www.storm.mg
www.wtorm.mg
www.swtorm.mg
www.wstorm.mg
www.etorm.mg
www.setorm.mg
www.estorm.mg
www.dtorm.mg
www.sdtorm.mg
www.dstorm.mg
www.ztorm.mg
www.sztorm.mg
www.zstorm.mg
www.xtorm.mg
www.sxtorm.mg
www.xstorm.mg
www.atorm.mg
www.satorm.mg
www.astorm.mg
www.sorm.mg
www.srorm.mg
www.strorm.mg
www.srtorm.mg
www.sform.mg
www.stform.mg
www.sftorm.mg
www.sgorm.mg
www.stgorm.mg
www.sgtorm.mg
www.syorm.mg
www.styorm.mg
www.sytorm.mg
www.strm.mg
www.stirm.mg
www.stoirm.mg
www.stiorm.mg
www.stkrm.mg
www.stokrm.mg
www.stkorm.mg
www.stlrm.mg
www.stolrm.mg
www.stlorm.mg
www.stprm.mg
www.stoprm.mg
www.stporm.mg
www.stom.mg
www.stoem.mg
www.storem.mg
www.stoerm.mg
www.stodm.mg
www.stordm.mg
www.stodrm.mg
www.stofm.mg
www.storfm.mg
www.stofrm.mg
www.stotm.mg
www.stortm.mg
www.stotrm.mg
www.stor.mg
www.storn.mg
www.stormn.mg
www.stornm.mg
www.storj.mg
www.stormj.mg
www.storjm.mg
www.stork.mg
www.stormk.mg
www.storkm.mg
www.storm.net
www.storm.org
www.storm.info
www.storm.biz
www.storm.us
www.storm.mobi
www.torm.mg
www.storm.mg
www.wtorm.mg
www.swtorm.mg
www.wstorm.mg
www.etorm.mg
www.setorm.mg
www.estorm.mg
www.dtorm.mg
www.sdtorm.mg
www.dstorm.mg
www.ztorm.mg
www.sztorm.mg
www.zstorm.mg
www.xtorm.mg
www.sxtorm.mg
www.xstorm.mg
www.atorm.mg
www.satorm.mg
www.astorm.mg
www.sorm.mg
www.srorm.mg
www.strorm.mg
www.srtorm.mg
www.sform.mg
www.stform.mg
www.sftorm.mg
www.sgorm.mg
www.stgorm.mg
www.sgtorm.mg
www.syorm.mg
www.styorm.mg
www.sytorm.mg
www.strm.mg
www.stirm.mg
www.stoirm.mg
www.stiorm.mg
www.stkrm.mg
www.stokrm.mg
www.stkorm.mg
www.stlrm.mg
www.stolrm.mg
www.stlorm.mg
www.stprm.mg
www.stoprm.mg
www.stporm.mg
www.stom.mg
www.stoem.mg
www.storem.mg
www.stoerm.mg
www.stodm.mg
www.stordm.mg
www.stodrm.mg
www.stofm.mg
www.storfm.mg
www.stofrm.mg
www.stotm.mg
www.stortm.mg
www.stotrm.mg
www.stor.mg
www.storn.mg
www.stormn.mg
www.stornm.mg
www.storj.mg
www.stormj.mg
www.storjm.mg
www.stork.mg
www.stormk.mg
www.storkm.mg