Skip to content
https://golsaplus.ir

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.

74

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.

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:317.007 label:Time to first byte subpart:timeToFirstByte] map[duration:4214.52 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-H1
nodeLabel: fff888 شثفا fff888
path: 1,HTML,1,BODY,2,DIV,0,DIV,3,MAIN,1,SECTION,4,DIV,0,DIV,0,DIV,0,DIV,1,H1
selector: div.grid > div.space-y-8 > div > h1.text-5xl
snippet: <h1 class="text-5xl md:text-6xl lg:text-7xl font-black leading-tight text-white drop-…">

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

RequestCache TTLTransfer Size
golsaplus.ir/uploads/general/1781472775472-j8114m.png86400.0 s1.3 KiB
golsaplus.ir/uploads/general/1781308480961-qvfmy.png?format=webp&w=1920&q=8086400.0 s673 B
golsaplus.ir/uploads/general/1781308480961-qvfmy.png?format=webp&w=192086400.0 s649 B
golsaplus.ir/uploads/general/1781472759212-0he4pc.jpg86400.0 s640 B
golsaplus.ir/uploads/general/1780613752302-hz6ldd.png86400.0 s632 B
golsaplus.ir/uploads/general/1781514697814-36qxt.png86400.0 s628 B
golsaplus.ir/uploads/general/1781514714848-3zslyp.jpg86400.0 s609 B
golsaplus.ir/uploads/general/1780265648740-7g0nzo.jpg86400.0 s596 B
golsaplus.ir/uploads/general/1781517487650-961ald.jpg?format=webp&w=60086400.0 s590 B
golsaplus.ir/uploads/general/1781308480961-qvfmy.png?format=webp&w=192086400.0 s0 B

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

Diagnostics

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.

Estimated savings: 40 ms 16.8 KiB
URLTransfer SizeEst Savings
golsaplus.ir/assets/index-YX64y73k.css20.0 KiB16.8 KiB

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: 80 ms 62.6 KiB
URLTransfer SizeEst Savings
golsaplus.ir/assets/vendor-other-OnUIyXOy.js54.8 KiB39.0 KiB
golsaplus.ir/assets/vendor-ui-CkOZBXJP.js31.4 KiB23.6 KiB

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 4.5 KiB
URLTransfer SizeEst Savings
golsaplus.ir/assets/vendor-icons-RbQmg7sa.js9.8 KiB4.5 KiB

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

●Time to Interactive 2.1 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify CSS
●Avoids enormous network payloads Total size was 604 KiB
●JavaScript execution time 0.3 s
●Minimizes main-thread work 0.8 s
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 90 ms
●Server Backend Latencies 1,520 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 110 ms
●Avoid large layout shifts 8 layout shifts found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
90

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
شماره تماس 09128855288 div.flex > div.flex > a > span
ورود div.container > div.flex > div.flex > a.inline-flex
fff888 یففاثیا div.grid > div.space-y-8 > div > span.whitespace-nowrap

These are opportunities to improve the legibility of your content.

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

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
٪33 تاج گل 3 طبقه مدل فاخر 22 ۲۰٬۰۰۰ تومان ۳۰٬۰۰۰ تومان div.flex > div.min-w-0 > div.h-full > a.group
٪89 تاج گل سه طبقه طرح دیپلمات ۱۵٬۰۰۰٬۰۰۰ تومان ۱۳۴٬۹۹۹٬۹۹۸ تومان div.flex > div.min-w-0 > div.h-full > a.group
٪6 تاج یک طبقه طرح نیلوفر ۸٬۰۰۰٬۰۰۰ تومان ۸٬۴۹۹٬۹۹۷ تومان div.flex > div.min-w-0 > div.h-full > a.group
٪99 تاج گل یک طبقه مدل سفیر امید ۶۰٬۰۰۰٬۰۰۰ تومان ۸۵٬۵۵۵٬۵۵۵٬۰۰۰ تومان div.flex > div.min-w-0 > div.h-full > a.group
٪33 ویژه تاج گل 3 طبقه مدل فاخر 22 ۲۰٬۰۰۰ تومان ۳۰٬۰۰۰ تومان div.flex > div.min-w-0 > div.h-full > a.group
٪89 ویژه تاج گل سه طبقه طرح دیپلمات ۱۵٬۰۰۰٬۰۰۰ تومان ۱۳۴٬۹۹۹٬۹۹۸ تومان div.flex > div.min-w-0 > div.h-full > a.group
٪99 ویژه تاج گل یک طبقه مدل سفیر امید ۶۰٬۰۰۰٬۰۰۰ تومان ۸۵٬۵۵۵٬۵۵۵٬۰۰۰ تومان div.flex > div.min-w-0 > div.h-full > a.group
ویژه تاج گل یک طبقه مدل سفیر ۵٬۰۰۰٬۰۰۰ تومان div.flex > div.min-w-0 > div.h-full > a.group
○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]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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
○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.
○`[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.
○Identical links have the same purpose.
○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.
100

Best Practices

●Uses HTTPS
●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
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Ensure proper origin isolation with COOP
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
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
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○Image elements have `[alt]` attributes

Send Feedback