Agah.com Site Title

کارگزاری آگاه | سرمایه‌گذاری، مدیریت دارایی، آموزش

Agah.com Meta Description

آگاه انتخاب نخست سرمایه‌گذاران بورس، سرمایه‌گذاری آسان و مطمئن، سبدگردانی اختصاصی، مدیریت صندوق‌های سرمایه‌گذاری، آموزش بورس

Agah.com Test Results

Agah.com Mobile Performance: 29/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources. Potential savings of 6,100 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Serve images in next-gen formats. Potential savings of 342 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Remove unused JavaScript. Potential savings of 298 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Reduce initial server response time. Root document took 1,380 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Minify JavaScript. Potential savings of 16 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Efficiently encode images. Potential savings of 35 KiB
Optimized images load faster and consume less cellular data. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 600 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 more.
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.
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.
Serve static assets with an efficient cache policy
74 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
4.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
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 more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks
10 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Keep request counts low and transfer sizes small
85 requests • 1,815 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
30 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Agah.com 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.

Agah.com Mobile Best Practices: 62/100
Quick overview:
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
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 servedover 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.
Includes front-end JavaScript libraries with known security vulnerabilities
19 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
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
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Agah.com Mobile Progressive Web App: 46/100
Quick overview:
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Installable
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 servedover 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.
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Agah.com Mobile Accessibility: 72/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 more.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
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 more.
Similar sites
Similar tests
www.agah.com
www.agah.net
www.agah.org
www.agah.info
www.agah.biz
www.agah.us
www.agah.mobi
www.gah.com
www.agah.com
www.qgah.com
www.aqgah.com
www.qagah.com
www.wgah.com
www.awgah.com
www.wagah.com
www.sgah.com
www.asgah.com
www.sagah.com
www.zgah.com
www.azgah.com
www.zagah.com
www.aah.com
www.afah.com
www.agfah.com
www.afgah.com
www.avah.com
www.agvah.com
www.avgah.com
www.atah.com
www.agtah.com
www.atgah.com
www.abah.com
www.agbah.com
www.abgah.com
www.ayah.com
www.agyah.com
www.aygah.com
www.ahah.com
www.aghah.com
www.ahgah.com
www.agh.com
www.agqh.com
www.agaqh.com
www.agqah.com
www.agwh.com
www.agawh.com
www.agwah.com
www.agsh.com
www.agash.com
www.agsah.com
www.agzh.com
www.agazh.com
www.agzah.com
www.aga.com
www.agab.com
www.agahb.com
www.agabh.com
www.agag.com
www.agahg.com
www.agagh.com
www.agay.com
www.agahy.com
www.agayh.com
www.agau.com
www.agahu.com
www.agauh.com
www.agaj.com
www.agahj.com
www.agajh.com
www.agan.com
www.agahn.com
www.aganh.com
www.agah.con
Last Tested: