Story119.com Test Results

Story119.com Mobile Performance: 57/100
Quick overview:
Time to Interactive
13.5 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 7,260 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
13,460 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Use video formats for animated content
Potential savings of 135 KiB
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 more about efficient video formats
Serve images in next-gen formats
Potential savings of 372 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.
Defer offscreen images
Potential savings of 245 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Reduce unused JavaScript
Potential savings of 42 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.
Properly size images
Potential savings of 199 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Avoid an excessive DOM size
880 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Reduce unused CSS
Potential savings of 25 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.
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
Serve static assets with an efficient cache policy
39 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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.
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`.
Minify CSS
Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Minify JavaScript
Potential savings of 2 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Efficiently encode images
Potential savings of 17 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

Story119.com Mobile SEO: 85/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
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 how to make links crawlable

Story119.com Mobile Best Practices: 72/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
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
36 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.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Story119.com Mobile Accessibility: 74/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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Select elements do not have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
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.
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.
Uses ARIA roles on incompatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have 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 about the `tabindex` attribute.
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.story119.com
www.story119.net
www.story119.org
www.story119.info
www.story119.biz
www.story119.us
www.story119.mobi
www.tory119.com
www.story119.com
www.wtory119.com
www.swtory119.com
www.wstory119.com
www.etory119.com
www.setory119.com
www.estory119.com
www.dtory119.com
www.sdtory119.com
www.dstory119.com
www.ztory119.com
www.sztory119.com
www.zstory119.com
www.xtory119.com
www.sxtory119.com
www.xstory119.com
www.atory119.com
www.satory119.com
www.astory119.com
www.sory119.com
www.srory119.com
www.strory119.com
www.srtory119.com
www.sfory119.com
www.stfory119.com
www.sftory119.com
www.sgory119.com
www.stgory119.com
www.sgtory119.com
www.syory119.com
www.styory119.com
www.sytory119.com
www.stry119.com
www.stiry119.com
www.stoiry119.com
www.stiory119.com
www.stkry119.com
www.stokry119.com
www.stkory119.com
www.stlry119.com
www.stolry119.com
www.stlory119.com
www.stpry119.com
www.stopry119.com
www.stpory119.com
www.stoy119.com
www.stoey119.com
www.storey119.com
www.stoery119.com
www.stody119.com
www.stordy119.com
www.stodry119.com
www.stofy119.com
www.storfy119.com
www.stofry119.com
www.stoty119.com
www.storty119.com
www.stotry119.com
www.stor119.com
www.stort119.com
www.storyt119.com
www.storg119.com
www.storyg119.com
www.storgy119.com
www.storh119.com
www.storyh119.com
www.storhy119.com
www.storu119.com
www.storyu119.com
www.storuy119.com
www.story19.com
www.story11.com
www.story119.con
Last Tested: