Ask.fm Ask and Answer - ASKfm
Find out what people want to know about you. Ask questions and get answers on any topic!
ask.fm Mobile Performance
60/100
These metrics represent real-world Chrome users experience viewing ask.fm 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 Input Delay
First Contentful Paint
Cumulative Layout Shift
Largest Contentful Paint
Metrics
Largest Contentful Paint33/100 4.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Time to Interactive57/100 6.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time58/100 530 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
First Contentful Paint65/100 3.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index90/100 3.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Cumulative Layout Shift100/100 0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (14)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript
Potential savings of 220 KiB
1,500 ms
Eliminate render-blocking resources
Potential savings of 930 ms
930 ms
Remove unused CSS
Potential savings of 58 KiB
300 ms
Serve images in next-gen formats
Potential savings of 37 KiB
150 ms
Defer offscreen images
Potential savings of 28 KiB
150 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Reduce the impact of third-party code
Third-party code blocked the main thread for 740 ms
Serve static assets with an efficient cache policy
5 resources found
Minimize main-thread work
2.5 s
Reduce JavaScript execution time
1.5 s
Avoid long main-thread tasks
8 long tasks found
Keep request counts low and transfer sizes small
25 requests • 642 KiB
Largest Contentful Paint element
1 element found
Avoid chaining critical requests
5 chains found
Passed Audits (14)
Minify JavaScript
Preload key requests
Enable text compression
Uses passive listeners to improve scrolling performance
Avoids `document.write()`
Avoids an excessive DOM size
68 elements
Initial server response time was short
Root document took 130 ms
Use video formats for animated content
Minify CSS
Preconnect to required origins
Avoid multiple page redirects
Potential savings of 630 ms
Avoids enormous network payloads
Total size was 642 KiB
Properly size images
Efficiently encode images
Potential savings of 14 KiB
ask.fm Mobile SEO
93/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)
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
Passed Audits (13)
Page isn’t blocked from indexing
Document uses legible font sizes
100% legible text
Links have descriptive text
Document has a valid `rel=canonical`
Tap targets are sized appropriately
100% appropriately sized tap targets
Document has a meta description
Document has a valid `hreflang`
Page has successful HTTP status code
Document has a `<title>` element
Document avoids plugins
Links are crawlable
robots.txt is valid
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
ask.fm Mobile Best Practices
77/100
These checks highlight opportunities to improve the overall code health of ask.fm 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 (3)
User Experience
Serves images with low resolution
Trust and Safety
Does not use HTTPS
1 insecure request found
Includes front-end JavaScript libraries with known security vulnerabilities
3 vulnerabilities detected
Passed Audits (11)
Avoids Application Cache
Avoids deprecated APIs
Detected JavaScript libraries
Displays images with correct aspect ratio
Properly defines charset
Links to cross-origin destinations are safe
Avoids requesting the notification permission on page load
Allows users to paste into password fields
Avoids requesting the geolocation permission on page load
No browser errors logged to the console
Page has the HTML doctype
ask.fm Mobile Progressive Web App
46/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 (9)
PWA Optimized
Manifest doesn't have a maskable icon
Is not configured for a custom splash screen
Does not set a theme color for the address bar.
Does not provide a valid `apple-touch-icon`
Installable
Does not register a service worker that controls page and `start_url`
Does not use HTTPS
1 insecure request found
Web app manifest does not meet the installability requirements
Fast and reliable
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
Passed Audits (5)
Page load is fast enough on mobile networks
Redirects HTTP traffic to HTTPS
Contains some content when JavaScript is not available
Content is sized correctly for the viewport
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
ask.fm Mobile Accessibility
46/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.
Image elements do not have `[alt]` attributes
Links do not have a discernible name
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.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (5)
`[aria-hidden="true"]` is not present on the document `<body>`
The page contains a heading, skip link, or landmark region
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has a `[lang]` attribute
Document has a `<title>` element
Mobile Usability
100/100
These checks validate how easily a visitor can use ask.fm 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).
Passed Audits (5)
Avoid plugins
Configure the viewport
Size content to viewport
Size tap targets appropriately
Use legible font sizes
Mobile Speed
67/100
These checks analyze the performance of ask.fm 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 (3)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Leverage browser caching
Minify JavaScript
Passed Audits (7)
Avoid landing page redirects
Enable compression
Reduce server response time
Minify CSS
Minify HTML
Optimize images
Prioritize visible content
www.ask.com
www.ask.net
www.ask.org
www.ask.info
www.ask.biz
www.ask.us
www.ask.mobi
www.sk.fm
www.ask.fm
www.qsk.fm
www.aqsk.fm
www.qask.fm
www.wsk.fm
www.awsk.fm
www.wask.fm
www.ssk.fm
www.assk.fm
www.sask.fm
www.zsk.fm
www.azsk.fm
www.zask.fm
www.ak.fm
www.awk.fm
www.aswk.fm
www.aek.fm
www.asek.fm
www.aesk.fm
www.adk.fm
www.asdk.fm
www.adsk.fm
www.azk.fm
www.aszk.fm
www.axk.fm
www.asxk.fm
www.axsk.fm
www.aak.fm
www.asak.fm
www.aask.fm
www.as.fm
www.asj.fm
www.askj.fm
www.asjk.fm
www.asi.fm
www.aski.fm
www.asik.fm
www.asm.fm
www.askm.fm
www.asmk.fm
www.asl.fm
www.askl.fm
www.aslk.fm
www.aso.fm
www.asko.fm
www.asok.fm
www.ask.net
www.ask.org
www.ask.info
www.ask.biz
www.ask.us
www.ask.mobi
www.sk.fm
www.ask.fm
www.qsk.fm
www.aqsk.fm
www.qask.fm
www.wsk.fm
www.awsk.fm
www.wask.fm
www.ssk.fm
www.assk.fm
www.sask.fm
www.zsk.fm
www.azsk.fm
www.zask.fm
www.ak.fm
www.awk.fm
www.aswk.fm
www.aek.fm
www.asek.fm
www.aesk.fm
www.adk.fm
www.asdk.fm
www.adsk.fm
www.azk.fm
www.aszk.fm
www.axk.fm
www.asxk.fm
www.axsk.fm
www.aak.fm
www.asak.fm
www.aask.fm
www.as.fm
www.asj.fm
www.askj.fm
www.asjk.fm
www.asi.fm
www.aski.fm
www.asik.fm
www.asm.fm
www.askm.fm
www.asmk.fm
www.asl.fm
www.askl.fm
www.aslk.fm
www.aso.fm
www.asko.fm
www.asok.fm