Speed Test › Overview ›
Speed Test
Overview
An overview of the speed test, highlighting key metrics and detailed performance insights.
Test Details
| Tested On | 6/5/2026, 11:01 PM UTC |
| Tested From | New York, USA |
| Test Device | Desktop PC (Chrome 136.0.7103.92) |
| Lighthouse | 12.6.0 |
| Requests | 17 |
| Page Size | 351 KB |
Web Vitals & Metrics
First Contentful Paint
0s - 0.9s
0.97s
1.6s+
Largest Contentful Paint
0s - 1.2s
2.02s
2.4s+
Total Blocking Time
0s
0.15s - 0.35s
0.35s+
Cumulative Layout Shift
0 - 0.1
0.1 - 0.25
0.308
Speed Index
1.07s
1.3s - 2.3ss
2.3s+s
Time To First Byte
0.35s
0.8s - 1.8s
1.8s+
Size Breakdown
JavaScript:
203 KB
Fonts:
131 KB
CSS:
8 KB
HTML:
7 KB
Other:
3 KB
Request Breakdown
JavaScript:
5
Other:
5
CSS:
3
Fonts:
2
HTML:
1
Slowest Local Resources
| URL | Load Time |
|---|---|
| https://aiscor.es/ | 1.47s |
| https://aiscor.es/assets/app.js | 0.26s |
| https://aiscor.es/api/get_dashboard.php | 0.14s |
| https://aiscor.es/assets/style.css | 0.14s |
| https://aiscor.es/favicon.ico | 0.12s |
Slowest External Resources
Visual Loading Progression
0.38s
0.75s
1.13s
1.5s
1.88s
2.25s
2.63s
3s
Performance Affecting Issues
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. .
Est savings of 280 ms
| URL | WASTED MS |
| https://mstats.pl | 281.55ms |
Largest Contentful Paint element
This is the largest contentful element painted within the viewport.
2,020 ms
Element
body > main.container > div.hero > h1
<h1 style="font-size: 3.5rem; font-weight: 800; letter-spacing: -0.05em;" x-text="t.idx_title">
| Phase | % of LCP | Timing |
| TTFB | 17% | 347.6ms |
| Load Delay | 0% | 0ms |
| Load Time | 0% | 0ms |
| Render Delay | 83% | 1670.13ms |
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].
4 layout shifts found
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. .
Est savings of 540 ms
| URL | Size | POTENTIAL SAVINGS |
| https://unpkg.com/[email protected]/dist/umd/lucide.min.js | 303 B | 314ms |
| https://cdn.jsdelivr.net/npm/chart.js | 71 KB | 384ms |
| https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&display=swap | 1 KB | 232ms |
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. .
Est savings of 63 KiB
| URL | Size | POTENTIAL SAVINGS |
| https://cdn.jsdelivr.net/npm/chart.js | 70 KB | 63 KB |
Use efficient cache lifetimes
A long cache lifetime can speed up repeat visits to your page. .
Est savings of 12 KiB
- https://cdn.jsdelivr.net/npm/chart.js
- https://mstats.pl/data/matomo.js
- https://cdn.jsdelivr.net/npm/[email protected]/dist/cdn.min.js
- https://aiscor.es/assets/print.css
- https://aiscor.es/assets/style.css
- https://aiscor.es/assets/app.js
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.
Optimize DOM size
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. .
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about [forced reflow] and its mitigations.
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.
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.
- https://unpkg.com/[email protected]/dist/umd/lucide.min.js
- https://aiscor.es/assets/style.css
- https://cdn.jsdelivr.net/npm/chart.js
- https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&display=swap
Serve static assets with an efficient cache policy
A long cache lifetime can speed up repeat visits to your page. .
6 resources found
| URL | CACHE TTL |
| https://cdn.jsdelivr.net/npm/chart.js | 7 Day |
| https://mstats.pl/data/matomo.js | 7 Day |
| https://cdn.jsdelivr.net/npm/[email protected]/dist/cdn.min.js | 7 Day |
| https://aiscor.es/assets/print.css | 7 Day |
| https://aiscor.es/assets/style.css | 7 Day |
| https://aiscor.es/assets/app.js | 7 Day |
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents [a 300 millisecond delay to user input]. .
Initial server response time was short
Keep the server response time for the main document short because all other requests depend on it. .
Root document took 110 ms
| URL | TIME SPENT |
https://aiscor.es/ | 109.5ms |
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. .
5 chains found
https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&display=swap
https://fonts.gstatic.com/s/inter/v20/UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa1ZL7W0Q5nw.woff2
0.04ms
https://fonts.gstatic.com/s/inter/v20/UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa25L7W0Q5n-wU.woff2
0.01ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. .
All text remains visible during webfont loads
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. .
Image elements have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS.
Avoids enormous network payloads
Large network payloads cost users real money and are highly correlated with long load times. .
Total size was 352 KiB
| URL | SIZE |
| https://unpkg.com/[email protected]/dist/umd/lucide.min.js | 92 KB |
| https://fonts.gstatic.com/s/inter/v20/UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa25L7W0Q5n-wU.woff2 | 83 KB |
| https://cdn.jsdelivr.net/npm/chart.js | 71 KB |
| https://fonts.gstatic.com/s/inter/v20/UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa1ZL7W0Q5nw.woff2 | 47 KB |
| https://mstats.pl/data/matomo.js | 21 KB |
| https://cdn.jsdelivr.net/npm/[email protected]/dist/cdn.min.js | 17 KB |
| https://aiscor.es/ | 7 KB |
| https://aiscor.es/assets/print.css | 4 KB |
| https://aiscor.es/assets/style.css | 3 KB |
| https://aiscor.es/config/lang/pl.json | 2 KB |
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. .
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. .
| URL | POTENTIAL SAVINGS |
Efficiently encode images
Optimized images load faster and consume less cellular data. .
Enable text compression
Enable Compression (Gzip/Brotli)
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. .
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
Avoids an excessive DOM size
A large DOM will increase memory usage, cause longer style calculations
| ELEMENTS | ||
| Total DOM Elements | 338 | |
| Maximum DOM Depth | <path d="M19.07 4.93A10 10 0 0 0 6.99 3.34"> | 8 |
| Maximum Child Elements | <div style="text-align:center;padding:10px;margin:20px 0;"> | 31 |
Avoids `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. .
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. .
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. .
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Optimize viewport for mobile
Tap interactions may be [delayed by up to 300 ms] if the viewport is not optimized for mobile.
Partly powered by Lighthouse.