Total
1.31 MB
34 requests
100% of total size
Screenshot captured after 2.35 s.
Vhex10 - En Hesaplı Yapı Marketi
See the website health and performance test results for https://www.vhex10.com/, including status code, load speed, SSL, WHOIS, DNS, console logs, Chrome UX Report, resource sizes, and Pagespeed findings.
Tested on 6 May 2026 08:39:53.
Up
- HTTP status 200
- Response time 471 ms
- Document load time 1.67 s
- Full page load time 2.35 s
- Document size 449.96 KB
- Full page size 720.77 KB
14/100
- Mobile score 14
- Desktop score 77
Observer's Performance Suggestions
Priority actions Observer identified from this test to improve speed, reliability, and user experience.
Poor mobile performance score (14/100)
Error
High Lighthouse rates this page as poor. Address render-blocking, image, and JavaScript audits below. Read more |
2 images served larger than displayed
Error
Medium 2 images are served at intrinsic dimensions more than 120% of their display size. Worst offender is 202% of display size. Resize images to match their rendered dimensions to save bandwidth. Read more |
No H1 element found
Error
Low The page is missing an <h1> tag. An H1 heading helps search engines and screen readers understand the primary topic of the page. Read more |
High Total Blocking Time (4306 ms)
Warning
High Long JavaScript tasks block the main thread, making the page feel unresponsive. Split long tasks, defer non-critical scripts, and reduce third-party JavaScript. Read more |
Slow Speed Index (9.0 s)
Warning
High The page takes too long to visually complete. Optimize critical rendering path, reduce render-blocking resources, and serve visible content first. Read more |
Mobile score is 63 points lower than desktop
Warning
High Desktop scores 77/100 but mobile only 14/100. Optimize for mobile CPU, network and viewport — most real-world traffic is mobile. Read more |
Missing Strict-Transport-Security header
Warning
High Without HSTS, browsers can be tricked into loading the site over plain HTTP, exposing traffic to interception. Add a Strict-Transport-Security header with a long max-age. Read more |
DOM has 3274 elements
Warning
High A large DOM increases memory usage and slows style calculations, layout, and repaints. Simplify the page structure, remove hidden elements, and lazy-render off-screen content. Read more |
Desktop performance needs improvement (77/100)
Warning
Medium Score is below 90. Tackle the highest-impact audits to push into the green. Read more |
Fewer than 75% of users have a good Time to First Byte
Warning
Medium Only 73% of real-user samples fall in the "good" bucket for Time to First Byte. Read more |
Only the top 10 of 22 suggestions are shown in the public test. To see all recommendations and track every change on your website, register now.
Did you know?
Observer tracks these signals every day and alerts you the moment something important changes. Register now.
8 Feb 2028
628 days left
8 Jul 2026
48 days left
Whois
- Registrar
- GoDaddy.com, LLC
- Created
- 8 Feb 2024
- Updated
- 13 Feb 2026
- Expires
- 8 Feb 2028
- Country
- US
- DNSSEC
- unsigned
SSL
- Issuer
- C=US,O=Google Trust Services,CN=WE1
- Subject
- CN=vhex10.com
- TLS version
- TLSv1.3
- Self-signed
- No
- Valid until
- 8 Jul 2026
DNS Records
Current DNS records returned for this domain at the time of the test.
- 104.19.156.83
- 104.19.157.83
No records returned.
- vhex10.com
- mx.uzmanposta.com
- ns31.myideasoft.com
- ns32.myideasoft.com
- google-site-verification=2idvW4qbx-zsgShGNlEG2SO7UaZO2g2Dj6yiOeEGNUc
- v=spf1 a mx include:_spf.uzmanposta.com ip4:185.122.12.0/24 ip4:185.122.13.0/24 -all
Resource Summary
Transfer size share of the tested page split by resource type.
Script
615.38 KB
12 requests
46% of total size
Image
325.24 KB
9 requests
24% of total size
Font
245.18 KB
6 requests
18% of total size
Stylesheet
111.7 KB
3 requests
8.4% of total size
Document
37.97 KB
1 requests
2.8% of total size
Other
1.9 KB
3 requests
0.1% of total size
Media
0 B
0 requests
0.0% of total size
Third-party
562.97 KB
15 requests
42% of total size
Total
1.22 MB
31 requests
100% of total size
Script
615.36 KB
12 requests
49% of total size
Image
309.67 KB
7 requests
25% of total size
Font
174.04 KB
5 requests
14% of total size
Stylesheet
111.6 KB
3 requests
8.9% of total size
Document
37.93 KB
1 requests
3.0% of total size
Other
1.9 KB
3 requests
0.2% of total size
Media
0 B
0 requests
0.0% of total size
Third-party
563.06 KB
15 requests
45% of total size
Core Web Vitals
Key performance signals from Lighthouse, with color-coded status for what is healthy and what still needs work.
The server starts responding quickly.
Users wait too long before any content appears.
Main visible content takes too long to appear.
Layout shifts are high and likely disruptive.
Visual loading is significantly delayed.
Heavy blocking is likely hurting responsiveness.
Potential input delay is high.
Users wait too long before the page responds.
TTFB
602 ms
FCP
3.19 s
LCP
8.34 s
TTI
9.63 s
The server starts responding quickly.
First visible content appears quickly.
Main visible content loads within the recommended range.
Layout shifts are high and likely disruptive.
Visible content fills the page quickly.
Main thread blocking stays in a healthy range.
Potential input delay stays low.
The page becomes interactive quickly.
TTFB
163 ms
FCP
807 ms
LCP
1.32 s
TTI
1.64 s
Loading Filmstrip
Visual loading progress from the Lighthouse run, shown in time order.
Google Pagespeed Insights
Switch between desktop and mobile Lighthouse results to review the latest performance findings for this page.
Mobile
14
Desktop
77
Audit Details
| Audit | Insight | Impact |
|---|---|---|
| Max Potential First Input Delay | 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. | 840 ms |
| Minimize main-thread work | Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work | 9.0 s |
| LCP request discovery | Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading | Open |
| Reduce unused JavaScript | Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| Est savings of 505 KiB |
| Avoid large layout shifts | These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
| 3 layout shifts found |
| Improve image delivery | Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| Est savings of 202 KiB |
| Network dependency tree | 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. | Open |
| Font display | Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
| Est savings of 80 ms |
| Render blocking requests | 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.
| Est savings of 1,070 ms |
| LCP breakdown | Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays. | Open |
| 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. Learn how to reduce unused CSS.
| Est savings of 104 KiB |
| Layout shift culprits | Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads. | Open |
| Forced reflow | 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.
| Open |
| Reduce JavaScript execution time | Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
| 5.0 s |
| Total Blocking Time | Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric. | 4,310 ms |
| Largest Contentful Paint | Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric | 8.3 s |
| Speed Index | Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric. | 9.0 s |
| Time to Interactive | 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. | 9.6 s |
| Cumulative Layout Shift | Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric. | 0.354 |
| First Contentful Paint | First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric. | 3.2 s |
| Minify JavaScript | Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
| Est savings of 2 KiB |
| Image elements do not have explicit `width` and `height` | Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
| Open |
Audit Details
| Audit | Insight | Impact |
|---|---|---|
| Forced reflow | 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.
| Open |
| Render blocking requests | 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.
| Est savings of 390 ms |
| Reduce unused JavaScript | Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| Est savings of 506 KiB |
| Network dependency tree | 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. | Open |
| Avoid large layout shifts | These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
| 3 layout shifts found |
| 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. Learn how to reduce unused CSS.
| Est savings of 105 KiB |
| Font display | Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
| Est savings of 30 ms |
| LCP request discovery | Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading | Open |
| Layout shift culprits | Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads. | Open |
| Cumulative Layout Shift | Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric. | 0.259 |
| Image elements do not have explicit `width` and `height` | Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
| Open |
| Improve image delivery | Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| Est savings of 149 KiB |
| Minify JavaScript | Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
| Est savings of 2 KiB |
| Total Blocking Time | Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric. | 180 ms |
| Largest Contentful Paint | Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric | 1.3 s |
Browser Console Logs
Messages captured from the browser console during the real page test.
Chrome UX Report
Real-user experience shares from recent Chrome visits to this website.
Origin: https://www.vhex10.com
Mobile 68.4%
Desktop 31.6%
Tablet 0.0%
| Metric | User experience share | 75th percentile |
|---|---|---|
| LCP |
Good 92.1%
Needs improvement 5.5%
Poor 2.4% | 1.43 s |
| INP |
Good 93.8%
Needs improvement 6.0%
Poor 0.2% | 86 ms |
| CLS |
Good 91.3%
Needs improvement 3.0%
Poor 5.8% | 0.01 |
| FCP |
Good 91.3%
Needs improvement 6.6%
Poor 2.1% | 1.18 s |
| TTFB |
Good 72.5%
Needs improvement 24.8%
Poor 2.7% | 825 ms |
Resources by Transfer Size
Largest transferred resources captured during the browser test, sorted from heaviest to lightest.
| Resource | Type | Status | Duration | Transfer size | Decoded size | Blocking |
|---|---|---|---|---|---|---|
| img | 200 | 19 ms | 190.91 KB | 190.62 KB | non-blocking | |
| script | 200 | 299 ms | 110.48 KB | 392.65 KB | non-blocking | |
| img | 200 | 612 ms | 104.56 KB | 104.27 KB | non-blocking | |
| link | 200 | 38 ms | 90.79 KB | 464.95 KB | blocking | |
| css | 200 | 17 ms | 70.61 KB | 70.31 KB | non-blocking | |
| css | 200 | 77 ms | 66.93 KB | 66.64 KB | non-blocking | |
| link | 200 | 34 ms | 31.08 KB | 85.48 KB | blocking | |
| link | 200 | 116 ms | 18.53 KB | 120.47 KB | blocking | |
| link | 200 | 98 ms | 6.61 KB | 18.79 KB | non-blocking | |
| script | 200 | 224 ms | 5.09 KB | 31.93 KB | non-blocking | |
| img | 200 | 702 ms | 4.19 KB | 3.9 KB | non-blocking | |
| script | 200 | 514 ms | 3.38 KB | 20.69 KB | non-blocking | |
| img | 200 | 32 ms | 3.01 KB | 2.71 KB | non-blocking | |
| img | 200 | 44 ms | 2.63 KB | 2.34 KB | non-blocking | |
| script | 0 | 372 ms | 2.37 KB | 5.04 KB | non-blocking | |
www.vhex10.com | other | 200 | 97 ms | 2.36 KB | 2.71 KB | non-blocking |
www.vhex10.com | other | 200 | 75 ms | 2.36 KB | 2.71 KB | non-blocking |
| script | 200 | 195 ms | 2.26 KB | 6.55 KB | non-blocking | |
| script | 200 | 196 ms | 1.14 KB | 1.96 KB | non-blocking | |
fonts.googleapis.com | css | 0 | 186 ms | 857 B | 2.99 KB | blocking |
| img | 0 | 45 ms | 342 B | 42 B | non-blocking | |
| img | 0 | 94 ms | 342 B | 42 B | non-blocking | |
www.googletagmanager.com | script | 0 | 165 ms | 0 B | 0 B | non-blocking |
www.googletagmanager.com | script | 0 | 722 ms | 0 B | 0 B | non-blocking |
| fetch | 0 | 259 ms | 0 B | 0 B | non-blocking | |
| fetch | 0 | 260 ms | 0 B | 0 B | non-blocking | |
www.googletagmanager.com | script | 0 | 279 ms | 0 B | 0 B | non-blocking |
| fetch | 0 | 167 ms | 0 B | 0 B | non-blocking | |
whatsappchat.ideasoft.dev | script | 0 | 104 ms | 0 B | 0 B | non-blocking |
Previous Test Results
Get daily monitoring and instant alerts with Observer.
Register Observer to keep testing your website automatically and react faster when something breaks.
Try Observer Discover