Gorilla.ua Site Title
...
Gorilla.ua Test Results
Gorilla.ua Mobile Performance: 28/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce JavaScript execution time
6.1 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.
Reduce unused JavaScript
Est savings of 447 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.
Largest Contentful Paint element
24,100 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Enable text compression
Est savings of 36 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Avoid large layout shifts
5 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Preload Largest Contentful Paint image
Est savings of 450 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Reduce the impact of third-party code
Third-party code blocked the main thread for 810 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.
Avoid multiple page redirects
Est savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Avoid an excessive DOM size
1,129 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.
Minimize main-thread work
8.6 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
Defer offscreen images
Est savings of 48 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.
Properly size images
Est savings of 44 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce unused CSS
Est savings of 23 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.
Serve static assets with an efficient cache policy
124 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid enormous network payloads
Total size was 3,531 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Avoid serving legacy JavaScript to modern browsers
Est savings of 64 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Document request latency
Est savings of 50 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Legacy JavaScript
Est savings of 48 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Layout shift culprits
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Use efficient cache lifetimes
Est savings of 780 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Forced reflow
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Time to Interactive
25.3 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
290 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.
Improve image delivery
Est savings of 266 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Gorilla.ua Mobile SEO: 92/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.
Gorilla.ua Mobile Best Practices: 59/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
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.
Uses third-party cookies
2 cookies found
Third-party cookies may be blocked in some contexts. Learn more about preparing for third-party cookie restrictions.
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.
Gorilla.ua Mobile Accessibility: 56/100
Quick overview:
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
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.
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.
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.
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.
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.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Similar sites
Similar tests
www.gorilla.com
www.gorilla.net
www.gorilla.org
www.gorilla.info
www.gorilla.biz
www.gorilla.us
www.gorilla.mobi
www.orilla.ua
www.gorilla.ua
www.forilla.ua
www.gforilla.ua
www.fgorilla.ua
www.vorilla.ua
www.gvorilla.ua
www.vgorilla.ua
www.torilla.ua
www.gtorilla.ua
www.tgorilla.ua
www.borilla.ua
www.gborilla.ua
www.bgorilla.ua
www.yorilla.ua
www.gyorilla.ua
www.ygorilla.ua
www.horilla.ua
www.ghorilla.ua
www.hgorilla.ua
www.grilla.ua
www.girilla.ua
www.goirilla.ua
www.giorilla.ua
www.gkrilla.ua
www.gokrilla.ua
www.gkorilla.ua
www.glrilla.ua
www.golrilla.ua
www.glorilla.ua
www.gprilla.ua
www.goprilla.ua
www.gporilla.ua
www.goilla.ua
www.goeilla.ua
www.goreilla.ua
www.goerilla.ua
www.godilla.ua
www.gordilla.ua
www.godrilla.ua
www.gofilla.ua
www.gorfilla.ua
www.gofrilla.ua
www.gotilla.ua
www.gortilla.ua
www.gotrilla.ua
www.gorlla.ua
www.gorulla.ua
www.goriulla.ua
www.goruilla.ua
www.gorjlla.ua
www.gorijlla.ua
www.gorjilla.ua
www.gorklla.ua
www.goriklla.ua
www.gorkilla.ua
www.gorolla.ua
www.goriolla.ua
www.goroilla.ua
www.gorila.ua
www.goripla.ua
www.gorilpla.ua
www.goriplla.ua
www.goriola.ua
www.gorilola.ua
www.gorikla.ua
www.gorilkla.ua
www.gorilpa.ua
www.gorillpa.ua
www.goriloa.ua
www.gorilloa.ua
www.gorilka.ua
www.gorillka.ua
www.gorill.ua
www.gorillq.ua
www.gorillaq.ua
www.gorillqa.ua
www.gorillw.ua
www.gorillaw.ua
www.gorillwa.ua
www.gorills.ua
www.gorillas.ua
www.gorillsa.ua
www.gorillz.ua
www.gorillaz.ua
www.gorillza.ua
www.gorilla.net
www.gorilla.org
www.gorilla.info
www.gorilla.biz
www.gorilla.us
www.gorilla.mobi
www.orilla.ua
www.gorilla.ua
www.forilla.ua
www.gforilla.ua
www.fgorilla.ua
www.vorilla.ua
www.gvorilla.ua
www.vgorilla.ua
www.torilla.ua
www.gtorilla.ua
www.tgorilla.ua
www.borilla.ua
www.gborilla.ua
www.bgorilla.ua
www.yorilla.ua
www.gyorilla.ua
www.ygorilla.ua
www.horilla.ua
www.ghorilla.ua
www.hgorilla.ua
www.grilla.ua
www.girilla.ua
www.goirilla.ua
www.giorilla.ua
www.gkrilla.ua
www.gokrilla.ua
www.gkorilla.ua
www.glrilla.ua
www.golrilla.ua
www.glorilla.ua
www.gprilla.ua
www.goprilla.ua
www.gporilla.ua
www.goilla.ua
www.goeilla.ua
www.goreilla.ua
www.goerilla.ua
www.godilla.ua
www.gordilla.ua
www.godrilla.ua
www.gofilla.ua
www.gorfilla.ua
www.gofrilla.ua
www.gotilla.ua
www.gortilla.ua
www.gotrilla.ua
www.gorlla.ua
www.gorulla.ua
www.goriulla.ua
www.goruilla.ua
www.gorjlla.ua
www.gorijlla.ua
www.gorjilla.ua
www.gorklla.ua
www.goriklla.ua
www.gorkilla.ua
www.gorolla.ua
www.goriolla.ua
www.goroilla.ua
www.gorila.ua
www.goripla.ua
www.gorilpla.ua
www.goriplla.ua
www.goriola.ua
www.gorilola.ua
www.gorikla.ua
www.gorilkla.ua
www.gorilpa.ua
www.gorillpa.ua
www.goriloa.ua
www.gorilloa.ua
www.gorilka.ua
www.gorillka.ua
www.gorill.ua
www.gorillq.ua
www.gorillaq.ua
www.gorillqa.ua
www.gorillw.ua
www.gorillaw.ua
www.gorillwa.ua
www.gorills.ua
www.gorillas.ua
www.gorillsa.ua
www.gorillz.ua
www.gorillaz.ua
www.gorillza.ua