Audit report for

soedja.com

Last audited on Jul 3, 2026

Performance needs significant improvement to meet modern standards

The site has a performance score of 45 and several critical issues including slow Largest Contentful Paint and high Total Blocking Time. SEO and accessibility scores are strong but could be further optimized. AI readiness is good with no blocking issues for crawlers.

0/100

Overall

05090100

Score profile

Category insights

Performance45

Largest Contentful Paint is slow at 4801ms and Total Blocking Time is high at 2737ms. Several opportunities exist to reduce JavaScript execution time and eliminate render-blocking requests.

SEO92

SEO score is 92 with only one link lacking descriptive text. No other critical SEO issues were found.

Accessibility94

Several accessibility issues were identified including insufficient color contrast, improper heading order, and missing alt text for SVG elements.

Best practices100

Best Practices score is 100 with no critical issues reported.

AI readiness100

All major AI crawlers are allowed and no technical barriers were found.

Performance metrics

4.8s

Largest Contentful Paint

Lab

0.03

Cumulative Layout Shift

Lab

2737ms

Total Blocking Time

Lab

1.1s

First Contentful Paint

Lab

1.8 MB

Page weight

Lab

1.10 g

CO2 per visit

Lab

Marketing readiness

Web analytics

Present

Advertising pixel

Present

Live chat

Missing

Blog or content

Present

Pricing page

Missing

Email capture

Present

AI crawler access

ChatGPT

Allowed

Claude

Allowed

Perplexity

Allowed

Gemini

Allowed

Common Crawl

Allowed

llms.txt

Present

Structured data

Present

Tech and tools detected

Google Analytics

Meta Pixel

Next.js

Social presence

Instagram

Facebook

Compare with competitors

Recommendations

18 issues found

High

Reduce unused JavaScript

Est savings of 270 KiB

Medium effort

How to fix

Use tree-shaking techniques to remove unused code. Analyze the bundle with Webpack or Vite to identify and eliminate dead code. Implement code splitting to load only necessary modules on demand.

Impact

Reduce initial load size by 270 KiB

Webpack

ViteTree-shaking

High

Improve image delivery

Est savings of 113 KiB

Medium effort

How to fix

Convert images to next-gen formats like WebP or AVIF. Use responsive images with srcset and sizes attributes. Implement lazy loading for off-screen images.

Impact

Reduce image payload by 113 KiB

WebPAVIFsrcsetlazy loading

High

Reduce JavaScript execution time

11.0 s

High effort

How to fix

Identify and optimize long-running tasks on the main thread. Use Web Workers for CPU-intensive operations. Defer non-critical JavaScript and use async or defer attributes where appropriate.

Impact

Reduce main-thread work by 11 seconds

Web Workersasyncdefer

High

Minimize main-thread work

14.7 s

High effort

How to fix

Profile the application using Chrome DevTools to identify long tasks. Optimize rendering logic and reduce layout thrashing. Use requestIdleCallback for non-urgent work.

Impact

Reduce main-thread work by 14.7 seconds

Chrome DevToolsrequestIdleCallback

High

Eliminate render-blocking requests

Est savings of 800 ms

Medium effort

How to fix

Defer non-critical CSS and JavaScript. Use asynchronous loading for scripts. Implement resource hints like preconnect and prefetch for external resources.

Impact

Reduce render-blocking time by 800 ms

asyncdeferpreconnectprefetch

Medium

Use efficient cache lifetimes

Est savings of 261 KiB

Low effort

How to fix

Configure HTTP caching headers for static assets. Set long cache durations for files that do not change frequently. Use Cache-Control and ETag headers to enable browser and CDN caching.

Impact

Reduce redundant downloads by 261 KiB

Cache-ControlETagHTTP headers

Medium

Fix color contrast ratio

Background and foreground colors do not have a sufficient contrast ratio

Low effort

How to fix

Use tools like Contrast Checker to identify low-contrast text. Adjust color values to meet WCAG AA or AAA standards. Ensure all text is readable against its background.

Impact

Improve accessibility for visually impaired users

Contrast CheckerWCAG guidelines

Medium

Ensure proper heading order

Heading elements are not in a sequentially-descending order

Low effort

How to fix

Review the HTML structure and ensure headings follow a logical hierarchy. Use h1 through h6 in order without skipping levels. Add ARIA roles where necessary for screen readers.

Impact

Improve navigation for screen reader users

HTML validatorARIA roles

Medium

Add accessible text alternatives for SVGs

SVG elements with an `img` role do not have an accessible text alternative

Low effort

How to fix

Add aria-label or aria-labelledby attributes to SVG elements used as images. Provide descriptive text for screen readers to convey the purpose of the image.

Impact

Improve accessibility for users relying on screen readers

aria-labelaria-labelledby

Medium

Remove duplicated JavaScript

Est savings of 7 KiB

Medium effort

How to fix

Analyze the JavaScript bundle for duplicate code. Use module bundlers like Webpack to deduplicate imports. Refactor shared code into common modules.

Impact

Reduce JavaScript size by 7 KiB

Webpackmodule bundlerscode refactoring

Medium

Optimize legacy JavaScript

Est savings of 69 KiB

Medium effort

How to fix

Replace outdated JavaScript patterns with modern equivalents. Update libraries to their latest versions. Remove deprecated code and replace it with efficient alternatives.

Impact

Reduce JavaScript size by 69 KiB

ES6+library updatescode refactoring

Medium

Preload critical resources

Initial server response time was short at 160 ms

Low effort

How to fix

Use <link rel="preload"> to prioritize loading of critical assets such as fonts, images, and scripts. Implement resource hints to guide the browser on which resources to load first.

Impact

Improve perceived performance and reduce load time

preloadresource hints

Medium

Implement HTTP/2 or HTTP/3

No specific issue identified but can improve performance

Medium effort

How to fix

Ensure the server supports HTTP/2 or HTTP/3. This reduces latency and improves the speed of asset delivery across multiple requests.

Impact

Reduce network latency and improve load times

HTTP/2HTTP/3server configuration

High

Optimize LCP timing

Largest Contentful Paint is slow at 4801ms

High effort

How to fix

Identify the largest content element and optimize its loading. Lazy load non-critical content. Reduce the size of large images and prioritize critical rendering path.

Impact

Reduce LCP time by up to 4.8 seconds

Lazy loadingimage optimizationcritical rendering path

See the full recommendations

Enter your email to unlock the prioritized recommendations and growth plan for this site.

soedja.com

Performance needs significant improvement to meet modern standards

See the full recommendations

Want us to fix this and grow your product?