This is a snapshot from a website aaghorizon.com taken at 2024/12/20 12:18:00
aaghorizon.com

Access to this page has been denied

px-captcha

Website info about aaghorizon.com

Network informations and whois lookup for aaghorizon.com

+

Network Info from aaghorizon.com

ContactSOA Serial
noc@alaskaair.com2014010739

E-Mail Account Settings for aaghorizon.com

Are you trying to figure out what is aaghorizon.com mailbox / mail account settings - find aaghorizon.com mail settings below.
Please keep in mind these informations gathered based on aaghorizon.com network settings, it mostly works and correct, but might contains errors.

Outgoing SMTP Settings for aaghorizon.com

HostPortSecurity Settings
smtp.office365.com587STARTTLS / TLS (Secure)

Incoming IMAP4 Settings for aaghorizon.com

HostPortSecurity Settings
outlook.office365.com993SSL (Secure)

Incoming POP3 Settings for aaghorizon.com

HostPortSecurity Settings
outlook.office365.com995SSL (Secure)

Free Website SEO analytics for aaghorizon.com

This session was sponsored by nPulse.net (AI) - the most advanced website analytics software

  • Blocked
  • DNS
  • Connect
  • SSL (TLS)
  • Send
  • Wait
  • Receive
0s2s4s6s8s10s12s355 ms1aaghorizon.com/1075 ms2www.alaskaair.com/84 ms3p2pcontent-fd-pro...ponent-base.css24 ms4resource.alaskaai...homelet.css769 ms5www.alaskaair.com...bf6b3b84622.css711 ms6www.alaskaair.com...a384ad73743.css774 ms7www.alaskaair.com...ed52fa7920d.css795 ms8www.alaskaair.com...2e71b8e303f.css732 ms9www.alaskaair.com...89e63988317.css128 ms10cdn.optimizely.com/js/10453949094.js60 ms11cdn.appdynamics.c...adrum-latest.js667 ms12www.alaskaair.com...eaderFooter.css603 ms13www.alaskaair.com...c76d270b633c.js677 ms14www.alaskaair.com...1c4680700a58.js628 ms15www.alaskaair.com...bcb71442e266.js528 ms16www.alaskaair.com...e703d3bfb756.js721 ms17www.alaskaair.com...90b87ca0d073.js697 ms18www.alaskaair.com...cede42990c79.js512 ms19www.alaskaair.com...191d76b5ff2a.js387 ms20www.alaskaair.com...80e1fd9c427d.js594 ms21www.alaskaair.com...bd03e32f1397.js594 ms22www.alaskaair.com...5d2391d91140.js680 ms23www.alaskaair.com...98d6dc19a709.js658 ms24www.alaskaair.com...f9b1c76f668e.js655 ms25www.alaskaair.com...a9b487a04807.js754 ms26www.alaskaair.com...bb665c713420.js680 ms27www.alaskaair.com...7485296392c0.js683 ms28www.alaskaair.com...c075de0c975f.js652 ms29www.alaskaair.com...uildManifest.js1318 ms30www.alaskaair.com..._ssgManifest.js220 ms31a10453949094.cdn....0453949094.html1618 ms32www.alaskaair.com...HeaderFooter.js159 ms33tags.tiqcdn.com...utag.js70 ms34images.contentsta...o_HolidayGC.jpg65 ms35images.contentsta..._cc_7172024.jpg172 ms36images.contentsta...way-hpmerch.jpg206 ms37images.contentsta...gTag_HPTile.jpg145 ms38resource.alaskaai...1x1pixel415 ms39resource.alaskaai...ane-tail-footer125 ms40www.alaskaair.com...cularWeb-Medium101 ms41www.alaskaair.com...ircularWeb-Book160 ms42www.alaskaair.com...rcularWeb-Light147 ms43logx.optimizely.com/v1/events1229 ms44contentcdnprodacc...index.js330 ms45p2pcontent-fd-pro...mponent-base.js72 ms46p2pcontent-fd-pro...main.js169 ms47dpm.demdex.net/id22 ms48tags.tiqcdn.com...utag.76.js25 ms49tags.tiqcdn.com...utag.140.js25 ms50tags.tiqcdn.com...utag.142.js26 ms51tags.tiqcdn.com...utag.185.js30 ms52tags.tiqcdn.com...utag.212.js22 ms53tags.tiqcdn.com...utag.346.js26 ms54tags.tiqcdn.com...utag.347.js25 ms55tags.tiqcdn.com...utag.410.js23 ms56tags.tiqcdn.com...utag.428.js22 ms57tags.tiqcdn.com...utag.455.js46 ms58tags.tiqcdn.com...utag.467.js49 ms59tags.tiqcdn.com...utag.486.js69 ms60tags.tiqcdn.com...utag.343.js72 ms61dpm.demdex.net/id/rd21 ms62resource.alaskaai...jquery.min.js325 ms63www.alaskaair.com...mponentsVersion343 ms64www.alaskaair.com...mponentsVersion346 ms65www.alaskaair.com...mponentsVersion354 ms66www.alaskaair.com...mponentsVersion363 ms67www.alaskaair.com...mponentsVersion365 ms68www.alaskaair.com...mponentsVersion373 ms69www.alaskaair.com...mponentsVersion376 ms70www.alaskaair.com...mponentsVersion379 ms71www.alaskaair.com...mponentsVersion381 ms72www.alaskaair.com...mponentsVersion382 ms73www.alaskaair.com...mponentsVersion120 ms74logx.optimizely.com/v1/events116 ms75resource.alaskaai...A08326D71.woff2130 ms76resource.alaskaai...44FDC542E.woff2129 ms77resource.alaskaai...1EFF86681.woff2784 ms78www.alaskaair.com...ng-interstitial46 ms79cdn.optimizely.co...gG9JbmWe1q.json56 ms80cdn.optimizely.co...c72bsd3FXY.json119 ms81s.swiftypecdn.com/install/v2/st.js645 ms82www.alaskaair.com...getloginstatus764 ms83geoservice.alaska...resolve779 ms84www.alaskaair.com..._mobile-ad825 ms85www.alaskaair.com...ersonalized-one461 ms86www.alaskaair.com...ersonalized-two25 ms87cdn.jsdelivr.net...credit-card.svg24 ms88cdn.jsdelivr.net...tion-stroke.svg18 ms89cdn.jsdelivr.net...ternal-link.svg9 ms90cdn.jsdelivr.net...mail.svg25 ms91cdn.jsdelivr.net...chat.svg44 ms92cdn.jsdelivr.net...phone.svg36 ms93cdn.jsdelivr.net...facebook.svg32 ms94cdn.jsdelivr.net...twitter.svg27 ms95cdn.jsdelivr.net...instagram.svg28 ms96cdn.jsdelivr.net...youtube.svg25 ms97cdn.jsdelivr.net...new-window.svg44 ms98alaskaairlines.demdex.net/dest5.html33 ms99somni.alaskaair.com/id51 ms100cm.everesttech.net/cm/dd44 ms101dpm.demdex.net...2VgQgAAACHhtAO577 ms1025584487.fls.doubl...8957701932.524470 ms1035584487.fls.doubl...8957701932.5244180 ms104www.googletagmanager.com/gtag/js14 ms105www.alaskaair.com/AlXMT4Ma/init.js148 ms106connect.facebook.net/en_US/fbevents.js339 ms107analytics.tiktok....events.js165 ms108cdn.quantummetric...um-alaskaair.js81 ms109js.adsrvr.org/up_loader.1.1.0.js123 ms110bat.bing.com/bat.js89 ms111collect.tealiumiq...i.gif17 ms112tags.tiqcdn.com/utag/tiqapp/utag.v.js30 ms1135584487.fls.doubl...9708924094.599644 ms114collect.tealiumiq...i.gif39 ms1155584487.fls.doubl...9708924094.599629 ms116resource.alaskaai...query-ui.min.js34 ms117unpkg.com...ton__bundled.js549 ms118unpkg.com...44 ms119unpkg.com...con__bundled.js524 ms120unpkg.com...32 ms121unpkg.com...ink__bundled.js226 ms122unpkg.com...214 ms123unpkg.com...umn__bundled.js150 ms124unpkg.com...24 ms125images.contentsta..._image_ver2.png23 ms126images.contentsta...ert_7172024.jpg13 ms127cdn.jsdelivr.net...evron-right.svg86 ms128visitor-service-e...06d001a0650059072 ms129visitor-service-e...06d001a0650059014 ms130s.swiftypecdn.com...39825302241.css32 ms131images.contentsta...ImageMerch1_2x21547 ms132unpkg.com...70 ms133unpkg.com...64 ms134unpkg.com...umn__bundled.js65 ms135bat.bing.com/p/action/4028467.js34 ms136connect.facebook....699295240276440151 ms137analytics.tiktok....E1OTI4NzI4MQ.js600 ms138www.alaskaair.com...SComHomeletHtml86 ms139adservice.google....8957701932.524494 ms140www.googletagmanager.com/gtag/js51 ms141www.google-analytics.com/analytics.js111 ms142www.googletagmanager.com/gtag/js23 ms143stk.px-cloud.net/ns181 ms144www.alaskaair.com...collector38 ms145unpkg.com...con-7a7490b8.js51 ms146adservice.google....9708924094.599644 ms147bat.bing.com/action/092 ms148bat.bing.com/action/090 ms149bat.bing.com/action/0607 ms150cc.swiftype.com/cc.js52 ms151www.facebook.com/tr/54 ms152www.facebook.com/tr/35 ms153www.google-analytics.com/collect30 ms154www.google-analytics.com/collect26 ms155www.google-analytics.com/j/collect158 ms156analytics.tiktok.com/api/v2/pixel25 ms157region1.analytics.google.com/g/collect26 ms158region1.analytics.google.com/g/collect147 ms159analytics.tiktok.com/api/v2/pixel/act8 ms160resource.alaskaai...homelet.css618 ms161resource.alaskaai...global44 ms162p2pcontent-fd-pro...main.js33 ms163p2pcontent-fd-pro...main.js11 ms164resource.alaskaai....scripts.min.js225 ms165www.alaskaair.com...collector72 ms166resource.alaskaai...global39 ms167resource.alaskaai...okie-consent.js54 ms168zn3xeyguhe8idwa8d...130 ms169insight.adsrvr.org/track/up9 ms170cdn.appdynamics.c...0071192b868c.js63 ms171siteintercept.qua...2947d8.chunk.js141 ms172siteintercept.qua...Targeting.php437 ms173ingest.quantummet...alaskaair421 ms174ingest.quantummet...alaskaair59 ms175siteintercept.qua...CoreModule.js349 ms176ingest.quantummet...alaskaair20 ms177siteintercept.qua...3cace1.chunk.js26 ms178siteintercept.qua...568f93.chunk.js206 ms179www.alaskaair.com...collector155 ms180ingest.quantummet...alaskaair154 ms181ingest.quantummet...alaskaair181 ms182www.alaskaair.com...collector
  • Blocked
  • DNS
  • Connect
  • SSL (TLS)
  • Send
  • Wait
  • Receive
0s2s4s6s8s10s12s364 ms1aaghorizon.com/1072 ms2www.alaskaair.com/82 ms3p2pcontent-fd-pro...ponent-base.css23 ms4resource.alaskaai...homelet.css765 ms5www.alaskaair.com...bf6b3b84622.css726 ms6www.alaskaair.com...a384ad73743.css775 ms7www.alaskaair.com...ed52fa7920d.css794 ms8www.alaskaair.com...2e71b8e303f.css750 ms9www.alaskaair.com...89e63988317.css131 ms10cdn.optimizely.com/js/10453949094.js67 ms11cdn.appdynamics.c...adrum-latest.js659 ms12www.alaskaair.com...eaderFooter.css44 ms13assets.contentsta...s-cp-styles.css680 ms14www.alaskaair.com...c76d270b633c.js831 ms15www.alaskaair.com...1c4680700a58.js103 ms16unpkg.com...top__bundled.js693 ms17www.alaskaair.com...bcb71442e266.js638 ms18www.alaskaair.com...e703d3bfb756.js857 ms19www.alaskaair.com...90b87ca0d073.js834 ms20www.alaskaair.com...cede42990c79.js619 ms21www.alaskaair.com...191d76b5ff2a.js511 ms22www.alaskaair.com...80e1fd9c427d.js678 ms23www.alaskaair.com...bd03e32f1397.js678 ms24www.alaskaair.com...5d2391d91140.js791 ms25www.alaskaair.com...98d6dc19a709.js817 ms26www.alaskaair.com...f9b1c76f668e.js813 ms27www.alaskaair.com...a9b487a04807.js911 ms28www.alaskaair.com...bb665c713420.js757 ms29www.alaskaair.com...7485296392c0.js796 ms30www.alaskaair.com...c075de0c975f.js684 ms31www.alaskaair.com...uildManifest.js1473 ms32www.alaskaair.com..._ssgManifest.js93 ms33unpkg.com...-AS-tagline.svg93 ms34unpkg.com...oneworld.svg173 ms35resource.alaskaai...user95 ms36images.contentsta...plane_final.png95 ms37images.contentsta...mileage_logo95 ms38images.contentsta...-Hero-White.svg1785 ms39www.alaskaair.com...HeaderFooter.js227 ms40a10453949094.cdn....0453949094.html184 ms41tags.tiqcdn.com...utag.js359 ms42images.contentsta...ayGC_mobile.jpg280 ms43resource.alaskaai...1x1pixel22 ms44www.alaskaair.com...rcularWeb-Light118 ms45logx.optimizely.com/v1/events1075 ms46contentcdnprodacc...index.js88 ms47dpm.demdex.net/id136 ms48dpm.demdex.net/id/rd287 ms49www.alaskaair.com...mponentsVersion285 ms50www.alaskaair.com...mponentsVersion287 ms51www.alaskaair.com...mponentsVersion291 ms52www.alaskaair.com...mponentsVersion294 ms53www.alaskaair.com...mponentsVersion294 ms54www.alaskaair.com...mponentsVersion295 ms55www.alaskaair.com...mponentsVersion298 ms56www.alaskaair.com...mponentsVersion302 ms57www.alaskaair.com...mponentsVersion305 ms58www.alaskaair.com...mponentsVersion313 ms59www.alaskaair.com...mponentsVersion131 ms60logx.optimizely.com/v1/events28 ms61resource.alaskaai...A08326D71.woff232 ms62resource.alaskaai...44FDC542E.woff236 ms63resource.alaskaai...1EFF86681.woff2721 ms64www.alaskaair.com...ng-interstitial78 ms65s.swiftypecdn.com/install/v2/st.js326 ms66www.alaskaair.com...getloginstatus711 ms67geoservice.alaska...resolve739 ms68www.alaskaair.com..._mobile-ad2338 ms69www.alaskaair.com...ersonalized-one1959 ms70www.alaskaair.com...ersonalized-two44 ms71alaskaairlines.demdex.net/dest5.html31 ms72somni.alaskaair.com/id42 ms73cm.everesttech.net/cm/dd56 ms74dpm.demdex.net...2VgQgAAANzqlgNx15 ms75www.alaskaair.com/AlXMT4Ma/init.js187 ms76www.googletagmanager.com/gtag/js128 ms77connect.facebook.net/en_US/fbevents.js234 ms78analytics.tiktok....events.js108 ms79js.adsrvr.org/up_loader.1.1.0.js152 ms80cdn.quantummetric...um-alaskaair.js114 ms81bat.bing.com/bat.js95 ms82collect.tealiumiq...i.gif43 ms835584487.fls.doubl...206737485.4800437 ms845584487.fls.doubl...515607673206.4723 ms85collect.tealiumiq...i.gif41 ms86unpkg.com...ton__bundled.js566 ms87unpkg.com...37 ms88unpkg.com...con__bundled.js536 ms89unpkg.com...31 ms90unpkg.com...ink__bundled.js252 ms91unpkg.com...23 ms92s.swiftypecdn.com...ZxvyeUDsqJ.json112 ms93unpkg.com...umn__bundled.js70 ms94unpkg.com...19 ms95images.contentsta...nterstitial.gif19 ms96images.contentsta...nterstitial.jpg14 ms97images.contentsta...ditcard_new.png1548 ms98unpkg.com...78 ms99unpkg.com...umn__bundled.js75 ms100unpkg.com...50 ms101visitor-service-e...06d001a0650059046 ms102visitor-service-e...06d001a0650059065 ms103stk.px-cloud.net/ns173 ms104www.alaskaair.com...collector165 ms105analytics.tiktok....E1OTI4NzI4MQ.js223 ms106www.alaskaair.com...SComHomeletHtml95 ms107region1.analytics.google.com/g/collect96 ms108stats.g.doubleclick.net/g/collect66 ms109www.googletagmanager.com/gtag/js66 ms110region1.analytics.google.com/g/collect111 ms111www.google.hu/ads/ga-audiences55 ms112adservice.google....206737485.4800453 ms113adservice.google....515607673206.4711 ms114www.facebook.com/tr/11 ms115www.facebook.com/tr/375 ms116cc.swiftype.com/cc.js52 ms117bat.bing.com/action/080 ms118bat.bing.com/action/044 ms119bat.bing.com/action/015 ms120analytics.tiktok....ify_45dd5971.js188 ms121www.alaskaair.com...collector182 ms122analytics.tiktok.com/api/v2/pixel248 ms123analytics.tiktok.com/api/v2/pixel/act126 ms124resource.alaskaai...global8 ms125www.google-analytics.com/collect8 ms126www.google-analytics.com/collect19 ms127zn3xeyguhe8idwa8d...54 ms128insight.adsrvr.org/track/up182 ms129www.alaskaair.com...collector135 ms130siteintercept.qua...Targeting.php327 ms131ingest.quantummet...alaskaair281 ms132ingest.quantummet...alaskaair128 ms133ingest.quantummet...alaskaair144 ms134ingest.quantummet...alaskaair143 ms135ingest.quantummet...alaskaair164 ms136www.alaskaair.com...collector

First Contentful Paint

First Contentful Paint marks the time at which the first text or image is painted.

Speed Index

Speed Index shows how quickly the contents of a page are visibly populated.

Largest Contentful Paint

Largest Contentful Paint marks the time at which the largest text or image is painted.

Time to Interactive

Time to interactive is the amount of time it takes for the page to become fully interactive.

Total Blocking Time

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Cumulative Layout Shift

Cumulative Layout Shift measures the movement of visible elements within the viewport.

Max Potential First Input Delay

The maximum potential First Input Delay that your users could experience is the duration of the longest task.

First Meaningful Paint

First Meaningful Paint measures when the primary content of a page is visible.

Eliminate render-blocking resources

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.

Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time.

Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.

Minify CSS

Minifying CSS files can reduce network payload sizes.

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time.

Reduce unused CSS

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.

Reduce unused JavaScript

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

Efficiently encode images

Optimized images load faster and consume less cellular data.

Serve images in next-gen formats

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.

Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.

Preconnect to required origins

Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins.

Initial server response time was short

Keep the server response time for the main document short because all other requests depend on it.

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded.

Preload key requests

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load.

Use HTTP/2

HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing.

Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes.

Remove duplicate modules in JavaScript bundles

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

Avoid serving legacy JavaScript to modern browsers

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. [Learn More](https://philipwalton.com/articles/deploying-es2015-code-in-production-today/)

Preload Largest Contentful Paint image

Preload the image used by the LCP element in order to improve your LCP time.

Avoids enormous network payloads

Large network payloads cost users real money and are highly correlated with long load times.

Uses efficient cache policy on static assets

A long cache lifetime can speed up repeat visits to your page.

Avoids an excessive DOM size

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow).

Avoid chaining critical requests

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.

User Timing marks and measures

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences.

JavaScript execution time

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.

Minimizes main-thread work

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

All text remains visible during webfont loads

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading.

Performance budget

Keep the quantity and size of network requests under the targets set by the provided performance budget.

Timing budget

Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly.

Keep request counts low and transfer sizes small

To set budgets for the quantity and size of page resources, add a budget.json file.

Minimize third-party usage

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.

Lazy load third-party resources with facades

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required.

Largest Contentful Paint element

This is the largest contentful element painted within the viewport. [Learn More](https://web.dev/lighthouse-largest-contentful-paint/)

Avoid large layout shifts

These DOM elements contribute most to the CLS of the page.

Uses passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance.

Avoids `document.write()`

For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds.

Avoid long main-thread tasks

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay.

Avoid non-composited animations

Animations which are not composited can be janky and increase CLS.

Image elements have explicit `width` and `height`

Set an explicit width and height on image elements to reduce layout shifts and improve CLS.

Network Requests

Lists the network requests that were made during page load.

Network Round Trip Times

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.

Server Backend Latencies

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.

Tasks

Lists the toplevel main thread tasks that executed during page load.

Diagnostics

Collection of useful page vitals.

Metrics

Collects all available metrics.

Screenshot Thumbnails

This is what the load of your site looked like.

Final Screenshot

The last screenshot captured of the pageload.

Script Treemap Data

Used for treemap app

`[accesskey]` values are unique

Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique.

`[aria-*]` attributes match their roles

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes.

`button`, `link`, and `menuitem` elements have accessible names

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.

`[aria-hidden="true"]` is not present on the document `<body>`

Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`.

`[aria-hidden="true"]` elements do not contain focusable descendents

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers.

ARIA input fields 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.

ARIA `meter` elements have accessible names

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.

ARIA `progressbar` elements have accessible names

When a `progressbar` 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.

`[role]`s have all required `[aria-*]` attributes

Some ARIA roles have required attributes that describe the state of the element to screen readers.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions.

`[role]`s are contained by their required parent element

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions.

`[role]` values are valid

ARIA roles must have valid values in order to perform their intended accessibility functions.

ARIA toggle fields have accessible names

When a toggle 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.

ARIA `tooltip` elements have accessible names

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.

ARIA `treeitem` elements have accessible names

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.

`[aria-*]` attributes have valid values

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values.

`[aria-*]` attributes are valid and not misspelled

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names.

Buttons 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.

The page contains a heading, skip link, or landmark region

Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently.

Background and foreground colors have a sufficient contrast ratio

Low-contrast text is difficult or impossible for many users to read.

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output.

Definition list items are wrapped in `<dl>` elements

Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them.

Document has a `<title>` element

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search.

`[id]` attributes on active, focusable elements are unique

All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies.

ARIA IDs are unique

The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies.

No form fields have multiple labels

Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels.

`<frame>` or `<iframe>` elements have a title

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

Heading elements appear 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.

`<html>` element has 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.

`<html>` element has a valid value for its `[lang]` attribute

Specifying a valid [BCP 47 language](https://www.w3.org/International/questions/qa-choosing-language-tags#question) helps screen readers announce text properly.

Image elements have `[alt]` attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute.

`<input type="image">` elements have `[alt]` text

When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button.

Form elements have associated labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers.

Links 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.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements

Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly.

The document does not use `<meta http-equiv="refresh">`

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience.

`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not 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.

`<object>` elements have `[alt]` text

Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users.

No element has a `[tabindex]` value greater than 0

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users.

`[lang]` attributes have a valid value

Specifying a valid [BCP 47 language](https://www.w3.org/International/questions/qa-choosing-language-tags#question) on elements helps ensure that text is pronounced correctly by a screen reader.

`<video>` elements contain a `<track>` element with `[kind="captions"]`

When a video provides a caption it is easier for deaf and hearing impaired users to access its information.

The page has a logical tab order

Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen.

Interactive controls are keyboard focusable

Custom interactive controls are keyboard focusable and display a focus indicator.

Interactive elements indicate their purpose and state

Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements.

The user's focus is directed to new content added to the page

If new content, such as a dialog, is added to the page, the user's focus is directed to it.

User focus is not accidentally trapped in a region

A user can tab into and out of any control or region without accidentally trapping their focus.

Custom controls have associated labels

Custom interactive controls have associated labels, provided by aria-label or aria-labelledby.

Custom controls have ARIA roles

Custom interactive controls have appropriate ARIA roles.

Visual order on the page follows DOM order

DOM order matches the visual order, improving navigation for assistive technology.

Offscreen content is hidden from assistive technology

Offscreen content is hidden with display: none or aria-hidden=true.

HTML5 landmark elements are used to improve navigation

Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology.

Uses HTTPS

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-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.

Links to cross-origin destinations are safe

Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities.

Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead.

Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead.

Avoids front-end JavaScript libraries with known security vulnerabilities ( 100 / 100 )

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers.

Ensure CSP is effective against XSS attacks

A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks.

Allows users to paste into password fields

Preventing password pasting undermines good security policy.

Displays images with correct aspect ratio

Image display dimensions should match natural aspect ratio.

Serves images with appropriate resolution

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity.

Fonts with `font-display: optional` are preloaded

Preload `optional` fonts so first-time visitors may use them.

Page has the HTML doctype

Specifying a doctype prevents the browser from switching to quirks-mode.

Properly defines charset

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Avoids `unload` event listeners

The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead.

Avoids Application Cache

Application Cache is deprecated.

Detected JavaScript libraries ( 100 / 100 )

All front-end JavaScript libraries detected on the page.

Avoids deprecated APIs

Deprecated APIs will eventually be removed from the browser.

No browser errors logged to the console

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns.

Page has valid source maps

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.

No issues in the `Issues` panel in Chrome Devtools

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Has a `<meta name="viewport">` tag with `width` or `initial-scale`

Add a `<meta name="viewport">` tag to optimize your app for mobile screens.

Document has a `<title>` element

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search.

Document has a meta description

Meta descriptions may be included in search results to concisely summarize page content.

Page has successful HTTP status code

Pages with unsuccessful HTTP status codes may not be indexed properly.

Links have descriptive text

Descriptive link text helps search engines understand your content.

Links are 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 More](https://support.google.com/webmasters/answer/9112205)

Page isn’t blocked from indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them.

robots.txt is valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed.

Image elements have `[alt]` attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute.

Document has a valid `hreflang`

hreflang links tell search engines what version of a page they should list in search results for a given language or region.

Document has a valid `rel=canonical`

Canonical links suggest which URL to show in search results.

Document uses legible font sizes

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px.

Document avoids plugins

Search engines can't index plugin content, and many devices restrict plugins or don't support them.

Tap targets are sized appropriately

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements.

Structured data is valid

Run the [Structured Data Testing Tool](https://search.google.com/structured-data/testing-tool/) and the [Structured Data Linter](http://linter.structured-data.org/) to validate structured data.

Web app manifest or service worker do not meet the installability requirements ( 0 / 100 )

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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement.

1 reason

Is not configured for a custom splash screen ( 0 / 100 )

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens.

Failures: No manifest was fetched.

Manifest doesn't have a maskable icon ( 0 / 100 )

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device.

No manifest was fetched

Registers 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.

Redirects HTTP traffic to HTTPS

If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users.

Sets a theme color for the address bar.

The browser address bar can be themed to match your site.

Content is sized correctly for the viewport

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens.

Has a `<meta name="viewport">` tag with `width` or `initial-scale`

Add a `<meta name="viewport">` tag to optimize your app for mobile screens.

Provides 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](https://web.dev/apple-touch-icon/).

Site works cross-browser

To reach the most number of users, sites should work across every major browser.

Page transitions don't feel like they block on the network

Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance.

Each page has a URL

Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media.

All rights reserved nPulse.net 2009 - 2025
Powered by: MVCP2 / BVCP / ASPF-MILTER / PHP 8.3 / NGINX / FreeBSD