Implement Resource Preloading Strategy

How to optimize logistico.jp

Generic SiteScore: 41/100Analyzed April 2026Re-analyze this site

Implement Resource Preloading Strategy

Medium Impact+8 points estimated

Why It Matters

Critical resources like the LCP image have 1.8 seconds of load delay due to late discovery.

How to Fix

Add preload hints for the hero image sakura-1.png in the HTML head section. Add fetchpriority='high' attribute to the LCP image element. Preconnect to external domains like unpkg.com and js.stripe.com to establish early connections.

0Poor

What This Score Means

A score of 41 falls in the "Poor" range (50-89). While it is better than poor (0-49), you should aim for 90+ to provide an optimal user experience and maximize SEO benefits.

This site is slower than approximately 35% of similar sites. The main issues affecting performance are image optimization, JavaScript execution time, and layout stability.

Addressing these issues could improve your conversion rate by 15-20% and boost your search engine rankings.

Core Web Vitals Analysis

LCP

Largest Contentful Paint

26.3s
Poor

Good: < 2.5s

Measures how long it takes for the main content to appear on screen

INP

Interaction to Next Paint

434ms
Needs Improvement

Good: < 200ms

Measures how quickly the page responds to user interactions

CLS

Cumulative Layout Shift

0.00
Good

Good: < 0.1

Measures visual stability - how much content shifts during page load

AI Performance Analysis

This website has severely poor performance with a score of just 41/100, indicating critical issues that significantly impact user experience. The biggest problem is an extremely slow loading speed - it takes over 26 seconds for the largest content to appear and 43 seconds for the page to become fully interactive, which is unacceptable for modern web standards. The site is loading massive amounts of unused CSS (175 KB) and JavaScript (816 KB), along with oversized images totaling over 17 MB, creating a bloated experience that wastes users' bandwidth and time. Immediate priorities should include removing unused code, compressing and properly sizing images, and implementing efficient caching - these optimizations alone could save over 13 MB and reduce load times by several seconds.

Other Optimization Recommendations

Optimize Large Image Files

High Impact+18 points estimated

Why It Matters:

Images consume 5.4MB and delay LCP by 1.6 seconds due to oversized gallery images.

How to Fix:

Compress gallery images using tools like TinyPNG or ImageOptim to reduce file sizes by 60-80%. Convert JPEGs to WebP format for better compression. Implement responsive images with srcset to serve appropriately sized images for different screen sizes.

Remove Unused CSS and JavaScript

High Impact+15 points estimated

Why It Matters:

816KB of unused JavaScript and 175KB of unused CSS are blocking render and delaying page load by 4+ seconds.

How to Fix:

Use webpack-bundle-analyzer to identify unused code in your build assets. Remove unused CSS rules from app-r8rlMTPf.css and inertia-R1wE83bg.css files. Code-split JavaScript bundles to load only necessary code initially and lazy-load remaining features.

Keep Your Site Fast After Optimization

Once your site is optimized, maintain that speed. Use DeployHQ for zero-downtime, automated deployments—so performance fixes and updates go live safely every time, without breaking your site.

Explore DeployHQ →Trusted by engineering teams shipping high-performance sites

Want to Analyze YOUR Website?

Get AI-powered performance insights with actionable fixes in 30 seconds

More Generic Speed Tests

Generic Performance Resources

Frequently Asked Questions