Skip to content
https://cloudavize5stg.wpenginepowered.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

99

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:30.362 source:map[column:10172 line:2240 type:source-location url:https://cloudavize5stg.wpenginepowered.com/ urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.302 source:map[column:50335 line:1 type:source-location url:https://cloudavize5stg.wpenginepowered.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.16 source:map[column:50393 line:1 type:source-location url:https://cloudavize5stg.wpenginepowered.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.132 source:map[column:50457 line:1 type:source-location url:https://cloudavize5stg.wpenginepowered.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:36.002 source:map[column:49615 line:1 type:source-location url:https://cloudavize5stg.wpenginepowered.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:10.674 source:map[column:31232 line:0 type:source-location url:https://cloudavize5stg.wpenginepowered.com/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=4.1.2 urlProvider:network]] map[reflowTime:28.798 source:map[column:7132 line:2239 type:source-location url:https://cloudavize5stg.wpenginepowered.com/ urlProvider:network]] map[reflowTime:1.246 source:map[column:17086 line:12 type:source-location url:https://cloudavize5stg.wpenginepowered.com/wp-content/plugins/elementor/assets/lib/swiper/v8/swiper.min.js?ver=8.4.5 urlProvider:network]] map[reflowTime:0.318 source:map[column:7508 line:12 type:source-location url:https://cloudavize5stg.wpenginepowered.com/wp-content/plugins/elementor/assets/lib/swiper/v8/swiper.min.js?ver=8.4.5 urlProvider:network]] map[reflowTime:0.975 source:map[column:10659 line:0 type:source-location url:https://cloudavize5stg.wpenginepowered.com/wp-content/plugins/elementor/assets/js/nested-tabs.a2401356d329f179475e.bundle.min.js urlProvider:network]]]

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Managed services div.elementor-column > div.elementor-widget-wrap > div.elementor-element > img.attachment-full
/wp-content/uploads/2025/08/managed-services-no-bg.webp44.6 KiB26.7 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 11.5 KiB
URLTransfer SizeEst Savings
/wp-content/themes/techbiz/assets/css/style.css?ver=2.7.0...57.4 KiB11.5 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 21.5 KiB
URLTransfer SizeEst Savings
/wp-content/plugins/elementor/assets/lib/swiper/v8/swiper...39.2 KiB21.5 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Time to Interactive 0.8 s
●Max Potential First Input Delay 40 ms
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,279 KiB
●JavaScript execution time 0.6 s
●Minimizes main-thread work 1.6 s
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 0 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 230 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
81

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Vincent Ortiz Business and Talent Specialist Vincent supports Cloudavize in cl… div.elementor-column > div.elementor-widget-wrap > div.elementor-element > div.swiper

When an element 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 how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.e-con-inner > div.elementor-element > div.elementor-element > a#custom-prev div.e-con-inner > div.elementor-element > div.elementor-element > a#custom-prev
div.e-con-inner > div.elementor-element > div.elementor-element > a#custom-next div.e-con-inner > div.elementor-element > div.elementor-element > a#custom-next

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.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-element > div.elementor-widget-container > div.header-btns > button.icon-btn div.elementor-element > div.elementor-widget-container > div.header-btns > button.icon-btn

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-column > div.elementor-widget-wrap > div.elementor-element > iframe div.elementor-column > div.elementor-widget-wrap > div.elementor-element > iframe

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Main (469) 250-1667 div.header-links > ul > li > a
Support (469) 728-0825 div.header-links > ul > li > a
Email: info@cloudavize.com div.header-links > ul > li > a
Get a Free Quote div.elementor-element > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Create Ticket div.elementor-element > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
As the top IT managed service provider in Dallas, TX since 2019, Cloudavize has… div.elementor-element > div.elementor-widget-container > div.title-area > p.desc
About Us div.elementor-element > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Contact Us form.wpcf7-form > div.form-wrap1 > div.form-style1 > h2.form-title
Or claim your free consultation today! div.form-wrap1 > div.form-style1 > div > a
24 HOURS SERVICE AVAILABLE  div.elementor-element > div.call-media > div.media-body > span.call-media__label
Why Choose Cloudavize For Dallas Managed IT Services div.elementor-element > div.elementor-widget-container > div.title-area > h2.sec-title3
READ MORE div.row > div.col-xl-4 > div.feature-style2 > a.link-btn
READ MORE div.row > div.col-xl-4 > div.feature-style2 > a.link-btn
READ MORE div.row > div.col-xl-4 > div.feature-style2 > a.link-btn
GET A FREE QUOTE FOR IT SOLUTIONS div.elementor-element > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
div.e-n-tabs > div.e-n-tabs-heading > button#e-n-tab-title-1049118251 > span.e-n-tab-title-text div.e-n-tabs > div.e-n-tabs-heading > button#e-n-tab-title-1049118251 > span.e-n-tab-title-text
div#accordionStyle6ad6cde6b66e2 > div.accordion-item > div#heading6968c986ad6cde6b66e2 > button.accordion-button div#accordionStyle6ad6cde6b66e2 > div.accordion-item > div#heading6968c986ad6cde6b66e2 > button.accordion-button
div.elementor-element > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text div.elementor-element > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
div.e-n-tabs > div.e-n-tabs-heading > button#e-n-tab-title-958063021 > span.e-n-tab-title-text div.e-n-tabs > div.e-n-tabs-heading > button#e-n-tab-title-958063021 > span.e-n-tab-title-text
div.elementor-element > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text div.elementor-element > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
TEAM MEMBERS div.elementor-element > div.elementor-widget-container > div.title-area > p.sec-subtitle
WHAT DALLAS SAYS ABOUT OUR MANAGED IT SERVICES div.elementor-element > div.elementor-widget-container > div.title-area > p.sec-subtitle
17. August, 2022. div.ti-inner > div.ti-review-header > div.ti-profile-details > div.ti-date
20. October, 2022. div.ti-inner > div.ti-review-header > div.ti-profile-details > div.ti-date
2. November, 2022. div.ti-inner > div.ti-review-header > div.ti-profile-details > div.ti-date
FAQS div.elementor-element > div.elementor-widget-container > div.title-area > p.sec-subtitle
What are Managed IT Services? div#accordionLayout1 > div.accordion-item > h2#accHead1 > button.accordion-button
WEEKLY UPDATES div.elementor-element > div.elementor-widget-container > div.title-area > p.sec-subtitle
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11989 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11989 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-12003 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-12003 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-17315 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-17315 > a

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.apo-ucar-on html.apo-ucar-on

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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 used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
61

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
https://cloudavize5stg.wpenginepowered.com/robots.txt

To appear in search results, crawlers need access to your app.

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback