Fruitsfamily.com Site Title

후루츠패밀리 - 빈티지, 세컨핸드 패션 중고거래 앱

Fruitsfamily.com Meta Description

유니크한 빈티지, 세컨핸드부터 구하기 힘든 하이엔드 디자이너 브랜드까지 후루츠에서 한번에.

Fruitsfamily.com Test Results

Fruitsfamily.com Mobile Performance: 48/100
Quick overview:
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
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. Learn how to avoid an excessive DOM size.
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.
Legacy JavaScript
Est savings of 27 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
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.
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.
Improve image delivery
Est savings of 2,039 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Use efficient cache lifetimes
Est savings of 35 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Time to Interactive
16.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
400 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.
Minimize main-thread work
3.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Reduce initial server response time
Root document took 1,520 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Reduce unused JavaScript
Est savings of 606 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Defer offscreen images
Est savings of 577 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Largest Contentful Paint element
7,150 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce the impact of third-party code
Third-party code blocked the main thread for 500 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 how to minimize third-party impact.
Serve images in next-gen formats
Est savings of 452 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Avoid multiple page redirects
Est savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Avoid an excessive DOM size
3,888 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Properly size images
Est savings of 3,926 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Avoid enormous network payloads
Total size was 10,375 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Reduce unused CSS
Est savings of 32 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Eliminate render-blocking resources
Est savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Serve static assets with an efficient cache policy
2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid serving legacy JavaScript to modern browsers
Est savings of 46 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling

Fruitsfamily.com Mobile SEO: 100/100
Quick overview:

Fruitsfamily.com Mobile Best Practices: 76/100
Quick overview:
General
Issues were logged in the `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.
Browser errors were 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 about this errors in console diagnostic audit
Missing source maps for large first-party JavaScript
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 about source maps.
Trust and Safety
Does not use HTTPS
1 insecure request found
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 about HTTPS.
Fruitsfamily.com Mobile Accessibility: 87/100
Quick overview:
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.fruitsfamily.com
www.fruitsfamily.net
www.fruitsfamily.org
www.fruitsfamily.info
www.fruitsfamily.biz
www.fruitsfamily.us
www.fruitsfamily.mobi
www.ruitsfamily.com
www.fruitsfamily.com
www.cruitsfamily.com
www.fcruitsfamily.com
www.cfruitsfamily.com
www.druitsfamily.com
www.fdruitsfamily.com
www.dfruitsfamily.com
www.rruitsfamily.com
www.frruitsfamily.com
www.rfruitsfamily.com
www.truitsfamily.com
www.ftruitsfamily.com
www.tfruitsfamily.com
www.gruitsfamily.com
www.fgruitsfamily.com
www.gfruitsfamily.com
www.vruitsfamily.com
www.fvruitsfamily.com
www.vfruitsfamily.com
www.fuitsfamily.com
www.feuitsfamily.com
www.freuitsfamily.com
www.feruitsfamily.com
www.fduitsfamily.com
www.frduitsfamily.com
www.ffuitsfamily.com
www.frfuitsfamily.com
www.ffruitsfamily.com
www.ftuitsfamily.com
www.frtuitsfamily.com
www.fritsfamily.com
www.fryitsfamily.com
www.fruyitsfamily.com
www.fryuitsfamily.com
www.frhitsfamily.com
www.fruhitsfamily.com
www.frhuitsfamily.com
www.frjitsfamily.com
www.frujitsfamily.com
www.frjuitsfamily.com
www.friitsfamily.com
www.fruiitsfamily.com
www.friuitsfamily.com
www.frutsfamily.com
www.fruutsfamily.com
www.fruiutsfamily.com
www.fruuitsfamily.com
www.frujtsfamily.com
www.fruijtsfamily.com
www.fruktsfamily.com
www.fruiktsfamily.com
www.frukitsfamily.com
www.fruotsfamily.com
www.fruiotsfamily.com
www.fruoitsfamily.com
www.fruisfamily.com
www.fruirsfamily.com
www.fruitrsfamily.com
www.fruirtsfamily.com
www.fruifsfamily.com
www.fruitfsfamily.com
www.fruiftsfamily.com
www.fruigsfamily.com
www.fruitgsfamily.com
www.fruigtsfamily.com
www.fruiysfamily.com
www.fruitysfamily.com
www.fruiytsfamily.com
www.fruitfamily.com
www.fruitwfamily.com
www.fruitswfamily.com
www.fruitwsfamily.com
www.fruitefamily.com
www.fruitsefamily.com
www.fruitesfamily.com
www.fruitdfamily.com
www.fruitsdfamily.com
www.fruitdsfamily.com
www.fruitzfamily.com
www.fruitszfamily.com
www.fruitzsfamily.com
www.fruitxfamily.com
www.fruitsxfamily.com
www.fruitxsfamily.com
www.fruitafamily.com
www.fruitsafamily.com
www.fruitasfamily.com
www.fruitsamily.com
www.fruitscamily.com
www.fruitsfcamily.com
www.fruitscfamily.com
www.fruitsdamily.com
www.fruitsfdamily.com
www.fruitsramily.com
www.fruitsframily.com
www.fruitsrfamily.com
www.fruitstamily.com
www.fruitsftamily.com
www.fruitstfamily.com
www.fruitsgamily.com
www.fruitsfgamily.com
www.fruitsgfamily.com
www.fruitsvamily.com
www.fruitsfvamily.com
www.fruitsvfamily.com
www.fruitsfmily.com
www.fruitsfqmily.com
www.fruitsfaqmily.com
www.fruitsfqamily.com
www.fruitsfwmily.com
www.fruitsfawmily.com
www.fruitsfwamily.com
www.fruitsfsmily.com
www.fruitsfasmily.com
www.fruitsfsamily.com
www.fruitsfzmily.com
www.fruitsfazmily.com
www.fruitsfzamily.com
www.fruitsfaily.com
www.fruitsfanily.com
www.fruitsfamnily.com
www.fruitsfanmily.com
www.fruitsfajily.com
www.fruitsfamjily.com
www.fruitsfajmily.com
www.fruitsfakily.com
www.fruitsfamkily.com
www.fruitsfakmily.com
www.fruitsfamly.com
www.fruitsfamuly.com
www.fruitsfamiuly.com
www.fruitsfamuily.com
www.fruitsfamjly.com
www.fruitsfamijly.com
www.fruitsfamkly.com
www.fruitsfamikly.com
www.fruitsfamoly.com
www.fruitsfamioly.com
www.fruitsfamoily.com
www.fruitsfamiy.com
www.fruitsfamipy.com
www.fruitsfamilpy.com
www.fruitsfamiply.com
www.fruitsfamioy.com
www.fruitsfamiloy.com
www.fruitsfamiky.com
www.fruitsfamilky.com
www.fruitsfamil.com
www.fruitsfamilt.com
www.fruitsfamilyt.com
www.fruitsfamilty.com
www.fruitsfamilg.com
www.fruitsfamilyg.com
www.fruitsfamilgy.com
www.fruitsfamilh.com
www.fruitsfamilyh.com
www.fruitsfamilhy.com
www.fruitsfamilu.com
www.fruitsfamilyu.com
www.fruitsfamiluy.com
www.fruitsfamily.con
Last Tested: