Audit report for

milan.co.id

Last audited on Jul 15, 2026

Performance and accessibility need significant improvements

The site has a performance score of 43 which is low. There are several opportunities to reduce unused JavaScript and CSS, minimize main thread work, and improve LCP. Accessibility scores are good but there are minor issues that should be addressed. The site is AI ready with good crawler access and structured data.

0/100
Overall
05090100

Score profile

Category insights

Performance43

The site has a performance score of 43. Largest Contentful Paint is slow at 14.9 seconds and layout shift is high at 0.231.

SEO85

The site has an SEO score of 85. There is one link without descriptive text which should be fixed.

Accessibility87

The site has an accessibility score of 87. There are some minor issues such as heading order and link names.

Best practices96

The site has a best practices score of 96. It serves images with low resolution which could be improved.

AI readiness95

The site is AI ready with good crawler access and structured data.

Performance metrics

14.9s
Largest Contentful Paint
Lab
0.23
Cumulative Layout Shift
Lab
184ms
Total Blocking Time
Lab
4.7s
First Contentful Paint
Lab
3.7 MB
Page weight
Lab
2.20 g
CO2 per visit
Lab

Marketing readiness

Web analytics

Present

Advertising pixel

Missing

Live chat

Missing

Blog or content

Present

Pricing page

Missing

Email capture

Missing

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 AnalyticsWordPress

Social presence

InstagramTikTokYouTubeFacebook

Compare with competitors

Recommendations

30 issues found
High

Remove unused JavaScript

Est savings of 325 KiB

How to fix

Identify and remove all unused JavaScript code. Use tools like Webpack or Rollup to analyze and split code. Implement code splitting and tree shaking to eliminate dead code.

Impact

Reduce page weight by 325 KiB and improve load time

WebpackRollupTree ShakingCode Splitting
High

Remove unused CSS

Est savings of 321 KiB

How to fix

Audit and remove unused CSS using tools like PurgeCSS or UnCSS. Implement critical CSS for above-the-fold content and defer non-critical CSS.

Impact

Reduce page weight by 321 KiB and improve load time

PurgeCSSUnCSSCritical CSSDefer CSS
High

Improve server response time

Root document took 410 ms

How to fix

Optimize server configuration, use a CDN, and implement HTTP/2 or HTTP/3. Ensure the server is properly configured for fast response times.

Impact

Reduce initial server response time and improve user experience

CDNHTTP/2HTTP/3Server Optimization
Medium

Minify JavaScript

Est savings of 20 KiB

How to fix

Use a minification tool like Terser or UglifyJS to compress JavaScript files. Ensure all JavaScript is minified before deployment.

Impact

Reduce JavaScript size by 20 KiB and improve load time

TerserUglifyJSMinification
Medium

Minify CSS

Est savings of 14 KiB

How to fix

Use a CSS minifier like CleanCSS or PostCSS to compress CSS files. Ensure all CSS is minified before deployment.

Impact

Reduce CSS size by 14 KiB and improve load time

CleanCSSPostCSSMinification
Medium

Implement efficient cache lifetimes

Est savings of 544 KiB

How to fix

Set appropriate cache headers for static assets. Use long cache lifetimes for resources that do not change frequently.

Impact

Reduce redundant downloads and improve load time

Cache HeadersCDNHTTP Caching
Medium

Improve font display

Est savings of 520 ms

How to fix

Use the 'swap' or 'optional' font-display value to prevent FOIT. Load critical fonts first and defer non-critical fonts.

Impact

Reduce layout shifts and improve perceived performance

Font DisplayWeb FontsCritical Font Loading
High

Reduce JavaScript execution time

1.4 s

How to fix

Identify and optimize long-running JavaScript tasks. Use Web Workers for heavy computations and avoid blocking the main thread.

Impact

Reduce JavaScript execution time by 1.4 s and improve responsiveness

Web WorkersAsync ProcessingJavaScript Optimization
High

Minimize main-thread work

4.4 s

How to fix

Profile and optimize main-thread work using Chrome DevTools. Defer non-essential scripts and use lazy loading for off-screen content.

Impact

Reduce main-thread work by 4.4 s and improve interactivity

Chrome DevToolsLazy LoadingDefer Scripts
Medium

Avoid large layout shifts

4 layout shifts found

How to fix

Ensure all elements have defined dimensions and avoid inserting content dynamically without预留 space. Use the 'loading' attribute for images and iframes.

Impact

Reduce layout shifts and improve user experience

Layout Shift AnalysisImage DimensionsLoading Attribute
Medium

Add descriptive text to links

1 link found

How to fix

Update the link to have descriptive text instead of generic text like 'click here'. Ensure all links have meaningful names.

Impact

Improve SEO and user experience

Link Text AuditSEO Best Practices
Medium

Ensure heading elements are in sequential order

Heading elements are not in a sequentially-descending order

How to fix

Review and restructure heading elements so they follow a logical hierarchy. Use H1 for the main title and subsequent headings in order.

Impact

Improve accessibility and screen reader compatibility

HTML ValidationAccessibility Testing
Medium

Ensure links have discernible names

Links do not have a discernible name

How to fix

Update links to have clear and descriptive text. Avoid using generic text like 'read more' without context.

Impact

Improve accessibility and user experience

Link Text AuditAccessibility Testing
Medium

Serve images with higher resolution

Serves images with low resolution

How to fix

Replace low-resolution images with higher-quality versions. Use responsive images with srcset and sizes attributes for optimal delivery.

Impact

Improve visual quality and user experience

Responsive Imagessrcsetsizes

Want us to fix this and grow your product?

Talk to Soedja