Zapatec.com Test Results

Zapatec.com Mobile Performance: 58/100
Quick overview:
Max Potential First Input Delay
1,000 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.
Time to Interactive
3.7 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.
Server Backend Latencies
80 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.
Metrics
Collects all available metrics.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Network Requests
Lists the network requests that were made during page load.
Final Screenshot
The last screenshot captured of the pageload.

658255435396

Script Treemap Data
Used for treemap app
Diagnostics
Collection of useful page vitals.
Network Round Trip Times
0 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.

Zapatec.com Mobile SEO: 85/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.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Page is blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Zapatec.com Mobile Best Practices: 92/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
General
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Zapatec.com Mobile PWA: 100/100
Quick overview:
Zapatec.com Mobile Accessibility: 76/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.
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.
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 about the `lang` attribute.
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.zapatec.com
www.zapatec.net
www.zapatec.org
www.zapatec.info
www.zapatec.biz
www.zapatec.us
www.zapatec.mobi
www.apatec.com
www.zapatec.com
www.xapatec.com
www.zxapatec.com
www.xzapatec.com
www.sapatec.com
www.zsapatec.com
www.szapatec.com
www.aapatec.com
www.zaapatec.com
www.azapatec.com
www.zpatec.com
www.zqpatec.com
www.zaqpatec.com
www.zqapatec.com
www.zwpatec.com
www.zawpatec.com
www.zwapatec.com
www.zspatec.com
www.zaspatec.com
www.zzpatec.com
www.zazpatec.com
www.zzapatec.com
www.zaatec.com
www.zaoatec.com
www.zapoatec.com
www.zaopatec.com
www.zalatec.com
www.zaplatec.com
www.zalpatec.com
www.zaptec.com
www.zapqtec.com
www.zapaqtec.com
www.zapqatec.com
www.zapwtec.com
www.zapawtec.com
www.zapwatec.com
www.zapstec.com
www.zapastec.com
www.zapsatec.com
www.zapztec.com
www.zapaztec.com
www.zapzatec.com
www.zapaec.com
www.zaparec.com
www.zapatrec.com
www.zapartec.com
www.zapafec.com
www.zapatfec.com
www.zapaftec.com
www.zapagec.com
www.zapatgec.com
www.zapagtec.com
www.zapayec.com
www.zapatyec.com
www.zapaytec.com
www.zapatc.com
www.zapatwc.com
www.zapatewc.com
www.zapatwec.com
www.zapatsc.com
www.zapatesc.com
www.zapatsec.com
www.zapatdc.com
www.zapatedc.com
www.zapatdec.com
www.zapatrc.com
www.zapaterc.com
www.zapate.com
www.zapatex.com
www.zapatecx.com
www.zapatexc.com
www.zapated.com
www.zapatecd.com
www.zapatef.com
www.zapatecf.com
www.zapatefc.com
www.zapatev.com
www.zapatecv.com
www.zapatevc.com
www.zapatec.con
Last Tested: