E-tibb.az Site Title

E-tibb.az - Online tibb kataloqu

E-tibb.az Meta Description

Azərbaycandakı həkimlər, klinika və apteklərlə bağlı məlumatlar, yüzlərlə həkim haqqında bilgi,tibbi məsləhətlər, həkimlərin bloqları

E-tibb.az Test Results

E-tibb.az Mobile Performance: 60/100
Quick overview:
First Meaningful Paint
7.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
15.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
210 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.
Server Backend Latencies
210 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Final Screenshot
The last screenshot captured of the pageload.

2060938125844

Network Requests
Lists the network requests that were made during page load.
Metrics
Collects all available metrics.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Diagnostics
Collection of useful page vitals.
Script Treemap Data
Used for treemap app
Network Round Trip Times
40 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.

E-tibb.az Mobile SEO: 92/100
Quick overview:
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 how to make pages mobile-friendly.
Tap targets are not sized appropriately
97% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

E-tibb.az Mobile Best Practices: 73/100
Quick overview:
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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
User Experience
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.
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
E-tibb.az Mobile PWA: 75/100
Quick overview:
PWA Optimized
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 about splash screens. Failures: Manifest does not have a PNG icon of at least 512px.
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 about maskable manifest icons.
E-tibb.az Mobile Accessibility: 72/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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
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.
Touch targets have sufficient size and 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.
All heading elements contain content.
A heading with no content or inaccessible text prevent screen reader users from accessing information on the page's structure. Learn more about headings.
Document has a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
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 have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. 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.
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.
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.e-tibb.com
www.e-tibb.net
www.e-tibb.org
www.e-tibb.info
www.e-tibb.biz
www.e-tibb.us
www.e-tibb.mobi
www.-tibb.az
www.e-tibb.az
www.w-tibb.az
www.ew-tibb.az
www.we-tibb.az
www.s-tibb.az
www.es-tibb.az
www.se-tibb.az
www.d-tibb.az
www.ed-tibb.az
www.de-tibb.az
www.r-tibb.az
www.er-tibb.az
www.re-tibb.az
www.etibb.az
www.e-ibb.az
www.e-ribb.az
www.e-tribb.az
www.e-rtibb.az
www.e-fibb.az
www.e-tfibb.az
www.e-ftibb.az
www.e-gibb.az
www.e-tgibb.az
www.e-gtibb.az
www.e-yibb.az
www.e-tyibb.az
www.e-ytibb.az
www.e-tbb.az
www.e-tubb.az
www.e-tiubb.az
www.e-tuibb.az
www.e-tjbb.az
www.e-tijbb.az
www.e-tjibb.az
www.e-tkbb.az
www.e-tikbb.az
www.e-tkibb.az
www.e-tobb.az
www.e-tiobb.az
www.e-toibb.az
www.e-tib.az
www.e-tivb.az
www.e-tibvb.az
www.e-tivbb.az
www.e-tigb.az
www.e-tibgb.az
www.e-tigbb.az
www.e-tihb.az
www.e-tibhb.az
www.e-tihbb.az
www.e-tinb.az
www.e-tibnb.az
www.e-tinbb.az
www.e-tibv.az
www.e-tibbv.az
www.e-tibg.az
www.e-tibbg.az
www.e-tibh.az
www.e-tibbh.az
www.e-tibn.az
www.e-tibbn.az
Last Tested: