Bpi.ir :: بانک پاسارگاد - بانک هزاره سوم ::
bpi.ir Mobile Performance
44/100
These metrics represent real-world Chrome users experience viewing bpi.ir 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 Contentful Paint
First Input Delay
Cumulative Layout Shift
Largest Contentful Paint
Metrics
Speed Index0/100 17.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint0/100 16.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First Contentful Paint39/100 4.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Time to Interactive59/100 6.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time98/100 190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift100/100 0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (19)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 1,609 KiB
6,900 ms
Properly size images
Potential savings of 950 KiB
4,800 ms
Efficiently encode images
Potential savings of 695 KiB
3,600 ms
Reduce initial server response time
Root document took 2,740 ms
2,136 ms
Eliminate render-blocking resources
Potential savings of 1,770 ms
1,770 ms
Avoid multiple page redirects
Potential savings of 1,110 ms
1,110 ms
Remove unused CSS
Potential savings of 62 KiB
300 ms
Remove unused JavaScript
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
Does not use passive listeners to improve scrolling performance
Avoid an excessive DOM size
1,522 elements
Minimize main-thread work
3.0 s
Serve static assets with an efficient cache policy
6 resources found
Avoids enormous network payloads
Total size was 2,674 KiB
JavaScript execution time
1.2 s
Avoid chaining critical requests
29 chains found
Keep request counts low and transfer sizes small
99 requests • 2,674 KiB
Largest Contentful Paint element
1 element found
Avoid long main-thread tasks
11 long tasks found
Passed Audits (9)
Defer offscreen images
Minify JavaScript
Potential savings of 13 KiB
Preconnect to required origins
Minimize third-party usage
Third-party code blocked the main thread for 20 ms
Avoids `document.write()`
Enable text compression
Minify CSS
Preload key requests
Use video formats for animated content
bpi.ir Mobile SEO
73/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 (4)
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Document doesn't use legible font sizes
27.11% legible text
Tap targets are not sized appropriately
87% appropriately sized tap targets
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
Document does not have a meta description
Passed Audits (8)
Page isn’t blocked from indexing
Links have descriptive text
Document avoids plugins
Links are crawlable
Page has successful HTTP status code
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document has a `<title>` element
Document has a valid `hreflang`
bpi.ir Mobile Best Practices
69/100
These checks highlight opportunities to improve the overall code health of bpi.ir 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 (4)
General
Browser errors were logged to the console
Trust and Safety
Links to cross-origin destinations are unsafe
Does not use HTTPS
1 insecure request found
Includes front-end JavaScript libraries with known security vulnerabilities
7 vulnerabilities detected
Passed Audits (10)
Properly defines charset
Allows users to paste into password fields
Avoids deprecated APIs
Avoids Application Cache
Displays images with correct aspect ratio
Detected JavaScript libraries
Avoids requesting the geolocation permission on page load
Page has the HTML doctype
Avoids requesting the notification permission on page load
Serves images with appropriate resolution
bpi.ir 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)
Fast and reliable
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
PWA Optimized
Is not configured for a custom splash screen
Manifest doesn't have a maskable icon
Does not set a theme color for the address bar.
Does not provide a valid `apple-touch-icon`
Installable
Web app manifest does not meet the installability requirements
Does not use HTTPS
1 insecure request found
Does not register a service worker that controls page and `start_url`
Passed Audits (5)
Contains some content when JavaScript is not available
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Page load is fast enough on mobile networks
Content is sized correctly for the viewport
Redirects HTTP traffic to HTTPS
bpi.ir Mobile Accessibility
78/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 (6)
Tables and lists
These are opportunities to 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>`).
List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
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
Buttons do not have an accessible name
Passed Audits (15)
`[aria-*]` attributes match their roles
`<html>` element has a `[lang]` attribute
`[aria-hidden="true"]` is not present on the document `<body>`
`<html>` element has a valid value for its `[lang]` attribute
`[role]`s have all required `[aria-*]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`[aria-*]` attributes are valid and not misspelled
Document has a `<title>` element
Heading elements appear in a sequentially-descending order
`[aria-*]` attributes have valid values
ARIA IDs are unique
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
The page contains a heading, skip link, or landmark region
Mobile Usability
99/100
These checks validate how easily a visitor can use bpi.ir 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).
Should Fix (1)
Size tap targets appropriately
Passed Audits (4)
Avoid plugins
Configure the viewport
Size content to viewport
Use legible font sizes
Mobile Speed
50/100
These checks analyze the performance of bpi.ir 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 (8)
Optimize images
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Minify JavaScript
Leverage browser caching
Minify HTML
Reduce server response time
Enable compression
Minify CSS
Passed Audits (2)
Avoid landing page redirects
Prioritize visible content
www.bpi.com
www.bpi.net
www.bpi.org
www.bpi.info
www.bpi.biz
www.bpi.us
www.bpi.mobi
www.pi.ir
www.bpi.ir
www.vpi.ir
www.bvpi.ir
www.vbpi.ir
www.gpi.ir
www.bgpi.ir
www.gbpi.ir
www.hpi.ir
www.bhpi.ir
www.hbpi.ir
www.npi.ir
www.bnpi.ir
www.nbpi.ir
www.bi.ir
www.boi.ir
www.bpoi.ir
www.bopi.ir
www.bli.ir
www.bpli.ir
www.blpi.ir
www.bp.ir
www.bpu.ir
www.bpiu.ir
www.bpui.ir
www.bpj.ir
www.bpij.ir
www.bpji.ir
www.bpk.ir
www.bpik.ir
www.bpki.ir
www.bpo.ir
www.bpio.ir
www.bpi.net
www.bpi.org
www.bpi.info
www.bpi.biz
www.bpi.us
www.bpi.mobi
www.pi.ir
www.bpi.ir
www.vpi.ir
www.bvpi.ir
www.vbpi.ir
www.gpi.ir
www.bgpi.ir
www.gbpi.ir
www.hpi.ir
www.bhpi.ir
www.hbpi.ir
www.npi.ir
www.bnpi.ir
www.nbpi.ir
www.bi.ir
www.boi.ir
www.bpoi.ir
www.bopi.ir
www.bli.ir
www.bpli.ir
www.blpi.ir
www.bp.ir
www.bpu.ir
www.bpiu.ir
www.bpui.ir
www.bpj.ir
www.bpij.ir
www.bpji.ir
www.bpk.ir
www.bpik.ir
www.bpki.ir
www.bpo.ir
www.bpio.ir