Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
Metrics
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Time to Interactive
0.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index
0.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time
30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Largest Contentful Paint
1.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Cumulative Layout Shift
0.007
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Show audits relevant to:
Diagnostics
Avoid chaining critical requests 5 chains found
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. Learn more.FCPLCP
Maximum critical path latency: 1,020 ms
Initial Navigation
/css/style.min.13ec410….css
- 360 ms, 14.01 KiB (buildsoftwaresystems.com)
/css2?family=…
(fonts.googleapis.com)
…v26/NGS6v5_NC….woff2
- 120 ms, 29.97 KiB (fonts.gstatic.com)
…v25/vEFO2_JTC….woff2
- 20 ms, 41.30 KiB (fonts.gstatic.com)
/js/script.min.f81e2fa….js
- 470 ms, 44.73 KiB (buildsoftwaresystems.com)
…dist/vanilla-back-to-top.min.js
- 70 ms, 1.75 KiB (unpkg.com)
Keep request counts low and transfer sizes small 22 requests • 577 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Resource Type | Requests | Transfer Size |
---|---|---|
Total | 22 | 577.1 KiB |
Font | 4 | 326.2 KiB |
Image | 3 | 90.6 KiB |
Script | 6 | 74.1 KiB |
Stylesheet | 4 | 46.5 KiB |
Other | 4 | 33.5 KiB |
Document | 1 | 6.1 KiB |
Media | 0 | 0.0 KiB |
Third-party | 11 | 336.5 KiB |
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element |
---|
Banner image <img loading="eager" decoding="async" src="https://buildsoftwaresystems.com/images/banner_hu60ea6e7d87a47498fce508e7a…" class="mx-auto lg:!max-w-[800px] img" alt="Banner image" width="1310" height="920"> |
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.CLS
Element | CLS Contribution |
---|---|
Learn and master software development <h1 class="mb-4"> | 0.005 |
Discover and master the technologies behind software engineering. Learn about v… <p class="mb-8"> | 0.002 |
Read Our Articles <a class="btn btn-primary" href="https://buildsoftwaresystems.com/post/"> | 0.001 |
Home
About
Articles
Pages
Contact <ul id="nav-menu" class="navbar-nav order-3 hidden lg:flex w-full pb-6 lg:order-1 lg:w-auto lg:spac…"> | 0 |
EN
FR
theme switcher <div class="order-1 ml-auto flex items-center md:order-2 lg:ml-0"> | 0 |
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn moreTBT
URL | Start Time | Duration |
---|---|---|
Unattributable | 630 ms | 72 ms |
Unattributable | 478 ms | 67 ms |
Passed audits (35) Show Hide
Passed audits (35)
Show Hide
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. Learn more.FCPLCP
Properly size images Potential savings of 31 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
URL | Resource Size | Potential Savings | |
---|---|---|---|
Banner image <img loading="eager" decoding="async" src="https://buildsoftwaresystems.com/images/banner_hu60ea6e7d87a47498fce508e7a…" class="mx-auto lg:!max-w-[800px] img" alt="Banner image" width="1310" height="920"> | /images/banner_hu60ea6e7…_332700_1110x0_resize_q90_h2_lanc….webp (buildsoftwaresystems.com) | 64.7 KiB | 31.1 KiB |
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Minify CSS
Minify JavaScript
Reduce unused CSS Potential savings of 40 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.FCPLCP
URL | Transfer Size | Potential Savings |
---|---|---|
/css/style-lazy.min.5d85e88….css (buildsoftwaresystems.com) | 28.7 KiB | 28.4 KiB |
/css/style.min.13ec410….css (buildsoftwaresystems.com) | 14.0 KiB | 11.3 KiB |
Reduce unused JavaScript Potential savings of 37 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.LCP
URL | Transfer Size | Potential Savings |
---|---|---|
/js/script.min.f81e2fa….js (buildsoftwaresystems.com) | 44.7 KiB | 37.1 KiB |
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.
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. Learn more.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.FCPLCP
Preconnect to required origins Warnings: - A `<link rel=preconnect>` was found for "https://use.fontawesome.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
- A `<link rel=preconnect>` was found for "https://www.googletagmanager.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
- A `<link rel=preconnect>` was found for "https://www.google-analytics.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
- More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
- A `<link rel=preconnect>` was found for "https://use.fontawesome.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
- A `<link rel=preconnect>` was found for "https://www.googletagmanager.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
- A `<link rel=preconnect>` was found for "https://www.google-analytics.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
- More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.FCPLCP
Initial server response time was short Root document took 240 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.FCPLCP
URL | Time Spent |
---|---|
240 ms |
Avoid multiple page redirects
Preload key requests
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.FCPLCP
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
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. Learn moreLCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. TBT
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn MoreTBT
URL | Potential Savings | |
---|---|---|
/js/script-lazy.min.c3e692e….js (buildsoftwaresystems.com) | 0.0 KiB | |
/js/script-lazy.min.c3e692e….js:5:512 (buildsoftwaresystems.com) | @babel/plugin-transform-classes |
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time. Learn more.LCP
URL | Potential Savings | |
---|---|---|
Banner image <img loading="eager" decoding="async" src="https://buildsoftwaresystems.com/images/banner_hu60ea6e7d87a47498fce508e7a…" class="mx-auto lg:!max-w-[800px] img" alt="Banner image" width="1310" height="920"> | /images/banner_hu60ea6e7…_332700_1110x0_resize_q90_h2_lanc….webp (buildsoftwaresystems.com) | 0 ms |
Avoids enormous network payloads Total size was 577 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.LCP
URL | Transfer Size |
---|---|
…webfonts/fa-solid-900.woff2 (cdnjs.cloudflare.com) | 147.3 KiB |
…webfonts/fa-brands-400.woff2 (cdnjs.cloudflare.com) | 107.7 KiB |
/images/banner_hu60ea6e7…_332700_1110x0_resize_q90_h2_lanc….webp (buildsoftwaresystems.com) | 65.1 KiB |
/js/script.min.f81e2fa….js (buildsoftwaresystems.com) | 44.7 KiB |
…v25/vEFO2_JTC….woff2 (fonts.gstatic.com) | 41.3 KiB |
/searchindex.json (buildsoftwaresystems.com) | 32.2 KiB |
…v26/NGS6v5_NC….woff2 (fonts.gstatic.com) | 30.0 KiB |
/css/style-lazy.min.5d85e88….css (buildsoftwaresystems.com) | 28.7 KiB |
/js/script-lazy.min.c3e692e….js (buildsoftwaresystems.com) | 19.3 KiB |
/css/style.min.13ec410….css (buildsoftwaresystems.com) | 14.0 KiB |
Uses efficient cache policy on static assets 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more.
URL | Cache TTL | Transfer Size |
---|---|---|
/count.js (gc.zgo.at) | 7 d | 3 KiB |
Avoids an excessive DOM size 150 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.TBT
Statistic | Element | Value |
---|---|---|
Total DOM Elements | 150 | |
Maximum DOM Depth | label > span > svg.absolute > path <path d="M30 4.6c0-1-.9-2-2-2a2 2 0 00-2 2v5c0 1 .9 2 2 2s2-1 2-2zm9.6 9a2 2 0 000 …"> | 9 |
Maximum Child Elements | body <body> | 15 |
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.TBT
URL | Total CPU Time | Script Evaluation | Script Parse |
---|---|---|---|
312 ms | 16 ms | 2 ms | |
Unattributable | 200 ms | 76 ms | 0 ms |
…js/index.js (buildsoftwaresystems.com) | 64 ms | 63 ms | 1 ms |
Minimizes main-thread work 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn moreTBT
Category | Time Spent |
---|---|
Style & Layout | 236 ms |
Script Evaluation | 186 ms |
Other | 166 ms |
Parse HTML & CSS | 21 ms |
Rendering | 17 ms |
Script Parsing & Compilation | 7 ms |
Garbage Collection | 1 ms |
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.FCPLCP
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.TBT
Third-Party | Transfer Size | Main-Thread Blocking Time |
---|---|---|
Cloudflare CDN | 255 KiB | 0 ms |
…webfonts/fa-solid-900.woff2 (cdnjs.cloudflare.com) | 147 KiB | 0 ms |
…webfonts/fa-brands-400.woff2 (cdnjs.cloudflare.com) | 108 KiB | 0 ms |
Google Fonts | 73 KiB | 0 ms |
…v25/vEFO2_JTC….woff2 (fonts.gstatic.com) | 41 KiB | 0 ms |
…v26/NGS6v5_NC….woff2 (fonts.gstatic.com) | 30 KiB | 0 ms |
Unpkg | 2 KiB | 0 ms |
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more.
Element |
---|
Banner image <img loading="eager" decoding="async" src="https://buildsoftwaresystems.com/images/banner_hu60ea6e7d87a47498fce508e7a…" class="mx-auto lg:!max-w-[800px] img" alt="Banner image" width="1310" height="920"> |
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Avoids document.write()
document.write()
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn moreCLS
Image elements have explicit width
and height
width
and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn moreCLS
Has a <meta name="viewport">
tag with width
or initial-scale
<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. Learn more.TBT
Avoids unload
event listeners
unload
event listeners The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Description | Directive | Severity |
---|---|---|
No CSP found in enforcement mode | High |
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name | Version |
---|---|
Workbox | 6.0.2 |
Passed audits (13) Show Hide
Passed audits (13)
Show Hide
Uses HTTPS
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.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.
Avoids front-end JavaScript libraries with known security vulnerabilities
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more.
No browser errors logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
No issues in the Issues
panel in Chrome Devtools
Issues
panel in Chrome Devtools 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.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
Not applicable (1) Show Hide
Not applicable (1)
Show Hide
Fonts with font-display: optional
are preloaded
font-display: optional
are preloaded Preload `optional` fonts so first-time visitors may use them. Learn more
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.
Additional items to manually check (1) Show Hide
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Passed audits (10) Show Hide
Passed audits (10)
Show Hide
Has a <meta name="viewport">
tag with width
or initial-scale
<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. Learn more.TBT
Document has a <title>
element
<title>
element The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn more.
Links are crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
Image elements have [alt]
attributes
[alt]
attributes Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Document has a valid hreflang
hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
Not applicable (4) Show Hide
Not applicable (4)
Show Hide
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.
Document has a valid rel=canonical
rel=canonical
Canonical links suggest which URL to show in search results. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more.
Tap targets are sized appropriately
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.