01M25YKY5WY3AGP8N1D4XHS9HG
Overall score
The website has several clear performance bottlenecks that noticeably slow down page rendering. Server and loading speed is the biggest problem here.
Browser runtime measurement
These values come from the real page build in the browser and show the differences between desktop and mobile.
Act now
Server response approx. 1984 ms
FCP approx. 2556 ms
205 requests during page load
First Contentful Paint approx. 2556 ms
54 JavaScript files are loaded synchronously and block page rendering.
Recommendation: Load scripts with an async or defer attribute wherever possible.
The browser issued 205 requests.
Recommendation: Above all, reduce or bundle tracking, builder assets, fonts and additional external services.
The server response takes around 1984 ms. That slows down page rendering very early on.
Recommendation: Check Full Page Cache, hosting performance and the WordPress backend.
The HTML directly references 91 CSS files and 61 external JavaScript files.
Recommendation: Reduce unnecessary assets and review the theme and plugin load.
Likely LCP image candidate
The largest visible content appears to be an image and can directly affect the page build.
Main causes
Actually loaded in the browser.
Top hosts by data volume
Largest requests
Total: 1.178,3 KB
Total: 982,5 KB
Recommendations
The server response takes around 1984 ms. A full page cache, a faster backend and less server-side work will likely have the biggest effect.
61 JavaScript files adding up to around 87.64 KB. Reduce unnecessary scripts, tracking and plugin front-end load, defer them or load them only when needed.
The real page load triggers 205 individual requests. Reduce unnecessary lazy loads, third parties and extra front-end files first.
sharoshop.com transfers around 195.82 KB more data on mobile than on desktop.
Recommendation: Check this host and the assets it loads on mobile and reduce them.
The First Contentful Paint is around 2556 ms.
Recommendation: Check early render blockers, server response and critical assets.
The Largest Contentful Paint is around 3000 ms.
Recommendation: Optimise the hero image, CSS, server response and JavaScript load.
sharoshop.com – 195.82 KB more data on mobile
Host: sharoshop.com
Largest Contentful Paint approx. 3000 ms
Hosts more prominent on mobile
sharoshop.com
Mobile 1.232,5 KB · Desktop 1.036,6 KB · Difference +195,8 KB
Explained simply
These short texts put the most important measurements into plain language.
The server responds slowly and stalls page rendering early on.
Why it matters: TTFB stands for “time to first byte” — the time until the server returns the first data.
Technical value: 1984 ms
The page is served compressed, so less data has to be transferred.
Why it matters: Compression reduces the transfer size of HTML, CSS and JavaScript.
Technical value: Content-Encoding: gzip
The browser is allowed to cache files, which can make repeat visits faster.
Why it matters: Browser caching prevents unchanged files from being downloaded over and over again.
Technical value: CSS: 10/10, JS: 15/15, images: 15/15, fonts: unknown | page cache: no, CDN: none detected, origin: nginx | HTML Cache-Control: max-age=0
41 images were detected. Of those, 3 use lazy loading and 0 use modern formats such as WebP or AVIF.
Why it matters: Images are often the biggest performance factor. Lazy loading and modern formats help the most.
Technical value: JPG: 14, PNG: 1 (12 of 41 measured), measured image weight: 618.48 KB
61 external JavaScript files were detected in the delivered HTML. Further scripts may only be loaded during the real page load through optimisation or lazy-load mechanisms.
Why it matters: Many or large JavaScript files can delay a page’s rendering and interactivity.
Technical value: 61 external files, 0 data URI scripts, 87.64 KB
12 font files were detected. In addition, 0 external font services (e.g. Google Fonts) are embedded.
Why it matters: Many or large web fonts increase loading time and can cause visible layout delays.
Technical value: 12 font files, 0 external font services, groups: no grouped fonts detected, measured font weight: 0 B
91 direct CSS files and 10 additional CSS dependencies were detected.
Why it matters: Many stylesheets or imported CSS files increase the number of loaded resources.
Technical value: Direct CSS files: 91, additional dependencies: 10, estimated CSS weight: 217.52 KB
The page loads content from 2 external hosts.
Why it matters: Every additional external domain increases dependencies and can affect loading time.
Technical value: no categories detected — logo.samandehi.ir, www.googletagmanager.com
The first visible content appears after around 2556 ms, the most important visible content after around 3000 ms. Visible page rendering is noticeably delayed.
Why it matters: These values describe when users actually see the first and the most important content.
Technical value: FCP: 2556 ms, LCP: 3000 ms
Layout stability is good. The measured CLS value is 0.
Why it matters: CLS describes whether content shifts visibly while loading.
Technical value: CLS: 0
The real page load issues very many requests and a noticeable amount of data: 205 requests with around 1.20 MB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 205 requests, 1.20 MB
Score breakdown
Speed
Cache quality by asset type
Statically detected external hosts
These hosts were detected directly in HTML or CSS. Not every one of them was necessarily loaded during the real page build.
Largest requests during the real page build
This list shows the largest requests from the real browser run and helps you spot notable files and hosts faster.
Technical metrics
Measurement conditions
Connection timing (TTFB: 1984 ms)
Tasks that blocked the browser main thread.
Details on individual metrics
In-depth values for assets, images, fonts, CSS and JavaScript. The most important groups are grouped thematically below.
This list shows the largest measured files from the asset check.
Sample: 12 of 41 images were loaded and measured. Size and count refer only to these images.
Detected font files: 11, External font services: 0. External font services are e.g. Google Fonts or Adobe Typekit, from which concrete font files are only loaded later.
These are stylesheets referenced within other CSS files via @import references.
These are the external script sources detected in the directly delivered HTML. Dynamically loaded scripts are not fully included.
Only the first 40 entries are shown.
WordPress detection
Optimisation potential
These points are not critical, but can improve the performance, stability or clarity of the page structure.
The browser main thread was blocked for around 340 ms during page load (Total Blocking Time).
Recommendation: Reduce JavaScript load, defer heavy scripts and break up long tasks.
The page contains 1856 DOM elements. Beyond roughly 1500 elements the browser slows down noticeably.
Recommendation: Reduce unnecessary wrapper elements and review the page builder output.
6 of 47 images have no explicit dimensions and can cause layout shifts (CLS).
Recommendation: Set width and height attributes on img tags.
HTML and CSS together reference 41 distinct images.
Recommendation: Optimise images, use lazy loading and remove unnecessary media.
No WebP or AVIF image files were detected in the HTML image sources.
Recommendation: Use WebP or AVIF for images where possible.
Detected 12 font files totalling around 0 B.
Recommendation: Load fewer font weights and serve fonts as efficiently as possible.
3 @font-face rules without font-display detected. Without font-display, text can stay invisible while loading (FOIT).
Recommendation: Add font-display: swap or optional to the @font-face rules.
Title: yes, H1: no, Viewport: yes.
Recommendation: Complete the basic HTML and SEO information.
Already done well
These points already stood out positively in the current scan.
Detected compression: gzip.
The website is reachable over HTTPS.
The website is served over HTTP/2.
Additional hints
Supplementary hints from the scan that can be useful for classification and technical assessment.
CSS pulls in 10 further stylesheet dependencies.
CSS references 11 additional font files.
The page uses WordPress, likely with elementor.
Detected theme: woodmart.
Detected indicators: woocommerce, elementor, wpbakery, rank-math.
The website is only reachable over IPv4.
Waterfall
Detailed request waterfall from the browser run.
Raw data
Complete scan data as a machine-readable JSON file or tabular export.