Skip to content
https://cofraje.net

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.

60

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

RequestCache TTLTransfer Size
connect.facebook.net/en_US/fbevents.js1200.0 s112.0 KiB
/signals/config/876125672550886?v=2.9.427&r=stable&domain...1200.0 s93.9 KiB
cofraje.net/wp-content/themes/betheme/js/plugins.js?ver=20.8.9.10.0 ms51.2 KiB
/wp-content/plugins/revslider/public/assets/js/jquery.the...0.0 ms36.3 KiB
cofraje.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.10.0 ms29.1 KiB
/wp-content/plugins/revslider/public/assets/js/jquery.the...0.0 ms16.9 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
cofraje.net/wp-content/themes/betheme/js/scripts.js?ver=20.8.9.10.0 ms13.6 KiB
cofraje.net/wp-content/themes/betheme/assets/jplayer/jplayer.min.js?ver=20.8.9.10.0 ms12.2 KiB
cofraje.net/wp-includes/js/dist/vendor/wp-polyfill.min.js?ver=3.15.00.0 ms11.3 KiB
cofraje.net/wp-content/themes/betheme/fonts/mfn-icons.woff?93978679604800.0 s79.1 KiB
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_wrapbg1-1.png604800.0 s73.2 KiB
/wp-content/uploads/2017/06/produse-fortza-cofraje-schele...604800.0 s72.4 KiB
/wp-content/plugins/cookie-law-info/legacy/public/js/cook...0.0 ms7.1 KiB
cofraje.net/wp-includes/js/jquery/ui/core.min.js?ver=1.13.30.0 ms6.7 KiB
cofraje.net/wp-includes/js/jquery/ui/sortable.min.js?ver=1.13.30.0 ms6.2 KiB
cofraje.net/wp-content/uploads/2017/06/cofraje-lemn.jpg604800.0 s60.0 KiB
cofraje.net/wp-includes/js/wp-emoji-release.min.js?ver=6.9.10.0 ms4.9 KiB
cofraje.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.10.0 ms4.6 KiB
/wp-content/uploads/2017/06/derspre-fortza-distribuitorul...604800.0 s39.8 KiB
cofraje.net/wp-content/plugins/contact-form-7/includes/js/index.js?ver=6.1.50.0 ms3.9 KiB
cofraje.net/wp-includes/js/jquery/ui/tabs.min.js?ver=1.13.30.0 ms3.8 KiB
cofraje.net/wp-content/plugins/contact-form-7/includes/swv/js/index.js?ver=6.1.50.0 ms3.3 KiB
cofraje.net/wp-includes/js/jquery/ui/accordion.min.js?ver=1.13.30.0 ms2.7 KiB
cofraje.net/wp-includes/js/dist/i18n.min.js?ver=c26c3dc7bed3667933750.0 ms2.1 KiB
cofraje.net/wp-content/themes/betheme/css/shortcodes.css?ver=20.8.9.1604800.0 s21.0 KiB
cofraje.net/wp-includes/js/dist/hooks.min.js?ver=dd5603f07f9220ed27f10.0 ms1.9 KiB
cofraje.net/wp-content/themes/betheme/css/layout.css?ver=20.8.9.1604800.0 s18.4 KiB
cofraje.net/wp-content/themes/betheme/js/parallax/translate3d.js?ver=20.8.9.10.0 ms1.6 KiB
cofraje.net/wp-content/themes/betheme/css/base.css?ver=20.8.9.1604800.0 s11.4 KiB
cofraje.net/wp-includes/js/jquery/ui/mouse.min.js?ver=1.13.30.0 ms1.0 KiB
cofraje.net/wp-content/themes/betheme/css/responsive.css?ver=20.8.9.1604800.0 s9.2 KiB
cofraje.net/wp-content/themes/betheme/js/menu.js?ver=20.8.9.10.0 ms839 B
cofraje.net/wp-content/uploads/2024/01/logo-fortza1x5w.png604800.0 s7.6 KiB
/wp-content/plugins/revslider/public/assets/css/settings....604800.0 s6.7 KiB
/wp-content/themes/betheme/assets/animations/animations.m...0.0 ms600 B
/wp-content/plugins/contact-form-7/modules/recaptcha/inde...0.0 ms449 B
/wp-content/themes/betheme/assets/animations/animations.m...604800.0 s4.4 KiB
/wp-content/plugins/cookie-law-info/legacy/public/css/coo...604800.0 s4.1 KiB
cofraje.net/wp-content/uploads/2022/03/logo-fortza-2022-alb-300x88.png604800.0 s4.0 KiB
cofraje.net/wp-content/themes/betheme/assets/ui/jquery.ui.all.css?ver=20.8.9.1604800.0 s3.0 KiB
/wp-content/themes/betheme/assets/jplayer/css/jplayer.blu...604800.0 s1.9 KiB
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_list1.png604800.0 s1.4 KiB
cofraje.net/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=6.1.5604800.0 s1006 B
/wp-content/plugins/cookie-law-info/legacy/public/css/coo...604800.0 s855 B
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_list3.png604800.0 s845 B
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_list4.png604800.0 s824 B
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_list5.png604800.0 s672 B
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_list6.png604800.0 s623 B
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_arrow_right.png604800.0 s559 B
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_list2.png604800.0 s467 B
cofraje.net/wp-content/plugins/revslider/public/assets/assets/coloredbg.png604800.0 s238 B
cofraje.net/wp-content/themes/cofraje/style.css?ver=20.8.9.1604800.0 s211 B
/tr/?id=876125672550886&ev=PageView&dl=https%3A%2F%2Fcofr...0.0 ms20 B
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_decoration1.png604800.0 s166 B
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_decoration2.png604800.0 s147 B
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_sep2.png604800.0 s111 B

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:61.553 source:map[column:27323 line:2 type:source-location url:https://cofraje.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 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:21.681 source:map[type:text value:[unattributed]]] map[reflowTime:37.918 source:map[column:49615 line:1 type:source-location url:https://cofraje.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:22.216 source:map[column:51395 line:1 type:source-location url:https://cofraje.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.578 source:map[column:52814 line:1 type:source-location url:https://cofraje.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:10.567 source:map[column:85575 line:1 type:source-location url:https://cofraje.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:1.746 source:map[column:79427 line:1 type:source-location url:https://cofraje.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:4.734 source:map[column:2352 line:103 type:source-location url:https://cofraje.net/wp-content/themes/betheme/js/plugins.js?ver=20.8.9.1 urlProvider:network]] map[reflowTime:4.652 source:map[column:2631 line:102 type:source-location url:https://cofraje.net/wp-content/plugins/revslider/public/assets/js/jquery.themepunch.tools.min.js?ver=5.4.3.1 urlProvider:network]] map[reflowTime:2.201 source:map[column:49637 line:1 type:source-location url:https://cofraje.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:1.44 source:map[column:3392 line:102 type:source-location url:https://cofraje.net/wp-content/plugins/revslider/public/assets/js/jquery.themepunch.tools.min.js?ver=5.4.3.1 urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1116.46 label:Time to first byte subpart:timeToFirstByte] map[duration:26.725 label:Resource load delay subpart:resourceLoadDelay] map[duration:591.496 label:Resource load duration subpart:resourceLoadDuration] map[duration:1215.012 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-DIV
nodeLabel: ul.tp-revslider-mainul > li.tp-revslider-slidesli > div.slotholder > div.tp-bgimg
path: 1,HTML,3,BODY,3,DIV,1,DIV,1,HEADER,3,DIV,0,DIV,1,DIV,0,UL,1,LI,1,DIV,1,DIV
selector: ul.tp-revslider-mainul > li.tp-revslider-slidesli > div.slotholder > div.tp-bgimg
snippet: <div class="tp-bgimg defaultimg " data-bgcolor="undefined" style="background-repeat: no-repeat; background-image: url(&quot;https://cofraje.net/w…&quot;);" src="https://cofraje.net/wp-content/uploads/2017/06/cofraje-lemn.jpg">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV
nodeLabel: ul.tp-revslider-mainul > li.tp-revslider-slidesli > div.slotholder > div.tp-bgimg
path: 1,HTML,3,BODY,3,DIV,1,DIV,1,HEADER,3,DIV,0,DIV,1,DIV,0,UL,1,LI,1,DIV,1,DIV
selector: ul.tp-revslider-mainul > li.tp-revslider-slidesli > div.slotholder > div.tp-bgimg
snippet: <div class="tp-bgimg defaultimg " data-bgcolor="undefined" style="background-repeat: no-repeat; background-image: url(&quot;https://cofraje.net/w…&quot;);" src="https://cofraje.net/wp-content/uploads/2017/06/cofraje-lemn.jpg">

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
value: no origins were preconnected
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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

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
Produse fortza.ro - cofraje, popi, furci, distantieri, cofraje metalice, cofraj… div.column_attr > div.image_frame > div.image_wrapper > img.scale-with-grid
/wp-content/uploads/2017/06/produse-fortza-cofraje-schele...72.3 KiB67.3 KiB
De peste 20 de ani ne dovedim profesionalismul . Avem probabil tot ce e necesar… div.entry-content > div.section > div.section_wrapper > div.wrap
www.cofraje.net/wp-content/uploads/2016/10/home_surveyor_wrapbg1-1.png73.1 KiB61.6 KiB
Fortza.Ro - distribuitorul de cofraje div.column_attr > div.image_frame > div.image_wrapper > img.scale-with-grid
/wp-content/uploads/2017/06/derspre-fortza-distribuitorul...39.8 KiB36.0 KiB
logo fortza1x5w div.top_bar_left > div.logo > a#logo > img.logo-main
cofraje.net/wp-content/uploads/2024/01/logo-fortza1x5w.png7.6 KiB4.3 KiB

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 170 ms 4.4 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.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.1 KiB
URLTransfer SizeEst Savings
cofraje.net/wp-content/themes/betheme/js/scripts.js?ver=20.8.9.113.6 KiB6.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
logo fortza1x5w div.top_bar_left > div.logo > a#logo > img.logo-main
cofraje.net/wp-content/uploads/2024/01/logo-fortza1x5w.png

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
●Modern HTTP
●Optimize viewport for mobile
●JavaScript execution time 0.9 s
●Minimizes main-thread work 1.7 s
●Avoid long main-thread tasks 4 long tasks found
●Avoid non-composited animations 14 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 190 ms
●Server Backend Latencies 160 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 550 ms
○INP breakdown
○User Timing marks and measures
○Avoid large layout shifts
78

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.

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
PRIMA PAGINA ul#menu-main-menu > li#menu-item-68 > a > span

These are opportunities to improve the legibility of your content.

Navigation

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Despre Fortza.Ro div.mcb-wrap-inner > div.column > div.column_attr > h4
Cofraje: Ușor de montat div.column > div.list_item > div.list_right > h4
Câteva informații despre firma FortzaRo. aside#text-4 > div.textwidget > div > h6
Sediul din Mediaș. div.column > aside#text-5 > div.textwidget > h6

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tp-loop-wrap > div.tp-mask-wrap > div#layer-757378180 > a div.tp-loop-wrap > div.tp-mask-wrap > div#layer-757378180 > a

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.

Best practices

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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.js html.js

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●Image elements have `[alt]` attributes
●`button`, `link`, and `menuitem` elements have accessible names
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○ARIA attributes are used as specified for the element's role
○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 use only permitted ARIA attributes
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○`<frame>` or `<iframe>` elements have a title
○`<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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○`[lang]` attributes have a valid value
○`<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.
73

Best Practices

Trust and Safety

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

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_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
ReferenceError: grecaptcha is not defined at HTMLDocument.<anonymous> (https://cofraje.net/wp-content/plugins/contact-form-7/modules/recaptcha/index.js?ver=6.1.5:1:470)

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content
●Avoids deprecated APIs
●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
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
100

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.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●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