Storm.mg 風傳媒 | Storm.mg
風傳媒擁有首屈一指、最強大、最優秀的編輯團隊及記者群，以最宏觀的視野掌握國際、國內的新聞、政治、兩岸動態，提供最優秀的原生新聞，讓使用者能看見最公正、真實的新聞內容，並且在本站發表個人的想法與見的，讓全世界都能聽見風傳媒網站中每一位會員的聲音。
storm.mg Mobile Performance
8/100
These metrics represent real-world Chrome users experience viewing storm.mg on mobile devices. 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
First Contentful Paint
Largest Contentful Paint
Cumulative Layout Shift
First Input Delay
Metrics
Speed Index0/100 28.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time0/100 5,020 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Time to Interactive0/100 61.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Largest Contentful Paint0/100 35.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First Contentful Paint23/100 5.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Cumulative Layout Shift98/100 0.055
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (21)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Defer offscreen images
Potential savings of 3,165 KiB
17,520 ms
Remove unused JavaScript
Potential savings of 1,050 KiB
13,520 ms
Serve images in next-gen formats
Potential savings of 1,151 KiB
6,300 ms
Eliminate render-blocking resources
Potential savings of 1,500 ms
1,500 ms
Remove unused CSS
Potential savings of 160 KiB
900 ms
Minify CSS
Potential savings of 11 KiB
180 ms
Enable text compression
Potential savings of 8 KiB
150 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid enormous network payloads
Total size was 10,030 KiB
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,150 ms
Avoid `document.write()`
Does not use passive listeners to improve scrolling performance
Ensure text remains visible during webfont load
Minimize main-thread work
31.7 s
Avoid an excessive DOM size
2,989 elements
Reduce JavaScript execution time
12.1 s
Serve static assets with an efficient cache policy
71 resources found
Largest Contentful Paint element
Avoid large layout shifts
Avoid chaining critical requests
84 chains found
Avoid long main-thread tasks
20 long tasks found
Keep request counts low and transfer sizes small
600 requests • 10,031 KiB
Passed Audits (8)
Use video formats for animated content
Preload key requests
Efficiently encode images
Properly size images
Preconnect to required origins
Initial server response time was short
Root document took 120 ms
Avoid multiple page redirects
Potential savings of 630 ms
Minify JavaScript
storm.mg Mobile SEO
91/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 (2)
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
88% appropriately sized tap targets
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Passed Audits (12)
Links have descriptive text
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document has a valid `hreflang`
Page isn’t blocked from indexing
Document has a `<title>` element
robots.txt is valid
Document has a meta description
Document avoids plugins
Document uses legible font sizes
100% legible text
Page has successful HTTP status code
Image elements have `[alt]` attributes
Document has a valid `rel=canonical`
storm.mg Mobile Best Practices
69/100
These checks highlight opportunities to improve the overall code health of storm.mg mobile 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
Links to cross-origin destinations are unsafe
Includes front-end JavaScript libraries with known security vulnerabilities
9 vulnerabilities detected
Does not use HTTPS
1 insecure request found
General
Browser errors were logged to the console
Passed Audits (10)
Avoids requesting the notification permission on page load
Serves images with appropriate resolution
Page has the HTML doctype
Avoids deprecated APIs
Avoids requesting the geolocation permission on page load
Displays images with correct aspect ratio
Detected JavaScript libraries
Properly defines charset
Allows users to paste into password fields
Avoids Application Cache
storm.mg Mobile Progressive Web App
21/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 provide a valid `apple-touch-icon`
Does not set a theme color for the address bar.
Is not configured for a custom splash screen
Installable
Does not register a service worker that controls page and `start_url`
Web app manifest does not meet the installability requirements
Does not use HTTPS
1 insecure request found
Fast and reliable
`start_url` does not respond with a 200 when offline
Current page does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive at 61.5 s
Passed Audits (4)
Redirects HTTP traffic to HTTPS
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Content is sized correctly for the viewport
Contains some content when JavaScript is not available
storm.mg Mobile Accessibility
91/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 (3)
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
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 (23)
The page contains a heading, skip link, or landmark region
`[role]`s are contained by their required parent element
`[aria-*]` attributes match their roles
`<html>` element has a `[lang]` attribute
`[aria-*]` attributes have valid values
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`[aria-hidden="true"]` elements do not contain focusable descendents
`[role]` values are valid
`<video>` elements contain a `<track>` element with `[kind="description"]`
`<html>` element has a valid value for its `[lang]` attribute
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[id]` attributes on active, focusable elements are unique
Image elements have `[alt]` attributes
`[aria-*]` attributes are valid and not misspelled
`<video>` elements contain a `<track>` element with `[kind="captions"]`
ARIA IDs are unique
`[role]`s have all required `[aria-*]` attributes
`[aria-hidden="true"]` is not present on the document `<body>`
Buttons have an accessible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Heading elements appear in a sequentially-descending order
Mobile Usability
99/100
These checks validate how easily a visitor can use storm.mg on a mobile device. Test results include a list of any mobile usability problems. Mobile usability problems are issues that can affect a user that visits the page on a mobile (small screen) device, including small font sizes (which are hard to read on a small screen).
Should Fix (1)
Size tap targets appropriately
Passed Audits (4)
Avoid plugins
Configure the viewport
Size content to viewport
Use legible font sizes
Mobile Speed
60/100
These checks analyze the performance of storm.mg on mobile devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (6)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Leverage browser caching
Optimize images
Minify HTML
Minify JavaScript
Enable compression
Passed Audits (4)
Avoid landing page redirects
Reduce server response time
Minify CSS
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