Kookas.ir Test Results

Kookas.ir Mobile Performance: 59/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Efficiently encode images
Potential savings of 103 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Minimize main-thread work
4.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Reduce JavaScript execution time
2.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce the impact of third-party code
Third-party code blocked the main thread for 320 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 how to minimize third-party impact.
Serve images in next-gen formats
Potential savings of 686 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.
Largest Contentful Paint element
4,080 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minify CSS
Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid an excessive DOM size
964 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.
Eliminate render-blocking resources
Potential savings of 320 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.
Properly size images
Potential savings of 15 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce unused CSS
Potential savings of 67 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.
Reduce initial server response time
Root document took 7,460 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Reduce unused JavaScript
Potential savings of 161 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.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 KiB
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 how to use modern JavaScript
Minify JavaScript
Potential savings of 7 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Serve static assets with an efficient cache policy
6 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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
Time to Interactive
9.9 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.
Max Potential First Input Delay
280 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
First Meaningful Paint
2.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Kookas.ir Mobile SEO: 85/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not 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 about robots.txt. Lighthouse was unable to download a robots.txt file
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.

Kookas.ir Mobile Best Practices: 52/100
Quick overview:
General
Uses third-party cookies
1 cookie found
Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.
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
Issues were logged 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.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Trust and Safety
Does not use HTTPS
1 insecure request 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.
Kookas.ir Mobile Accessibility: 81/100
Quick overview:
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.
ARIA input fields do not 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 about input field labels.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not 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 about heading order.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
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
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.
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.
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 tests
www.kookas.com
www.kookas.net
www.kookas.org
www.kookas.info
www.kookas.biz
www.kookas.us
www.kookas.mobi
www.ookas.ir
www.kookas.ir
www.jookas.ir
www.kjookas.ir
www.jkookas.ir
www.iookas.ir
www.kiookas.ir
www.ikookas.ir
www.mookas.ir
www.kmookas.ir
www.mkookas.ir
www.lookas.ir
www.klookas.ir
www.lkookas.ir
www.oookas.ir
www.koookas.ir
www.okookas.ir
www.kokas.ir
www.kiokas.ir
www.koiokas.ir
www.kkokas.ir
www.kokokas.ir
www.kkookas.ir
www.klokas.ir
www.kolokas.ir
www.kpokas.ir
www.kopokas.ir
www.kpookas.ir
www.koikas.ir
www.kooikas.ir
www.kokkas.ir
www.kookkas.ir
www.kolkas.ir
www.koolkas.ir
www.kopkas.ir
www.koopkas.ir
www.kooas.ir
www.koojas.ir
www.kookjas.ir
www.koojkas.ir
www.kooias.ir
www.kookias.ir
www.koomas.ir
www.kookmas.ir
www.koomkas.ir
www.koolas.ir
www.kooklas.ir
www.koooas.ir
www.kookoas.ir
www.kooks.ir
www.kookqs.ir
www.kookaqs.ir
www.kookqas.ir
www.kookws.ir
www.kookaws.ir
www.kookwas.ir
www.kookss.ir
www.kookass.ir
www.kooksas.ir
www.kookzs.ir
www.kookazs.ir
www.kookzas.ir
www.kooka.ir
www.kookaw.ir
www.kookasw.ir
www.kookae.ir
www.kookase.ir
www.kookaes.ir
www.kookad.ir
www.kookasd.ir
www.kookads.ir
www.kookaz.ir
www.kookasz.ir
www.kookax.ir
www.kookasx.ir
www.kookaxs.ir
www.kookaa.ir
www.kookasa.ir
www.kookaas.ir
Last Tested: