Fanbox.cc Site Title

pixivFANBOX(ファンボックス)

Fanbox.cc Meta Description

クリエイターの創作活動を支えるファンコミュニティ「pixivFANBOX」

Fanbox.cc Test Results

Fanbox.cc Mobile Performance: 19/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats. Potential savings of 1,450 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Remove unused JavaScript. Potential savings of 717 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Reduce initial server response time. Root document took 1,350 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Eliminate render-blocking resources. Potential savings of 930 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Efficiently encode images. Potential savings of 40 KiB
Optimized images load faster and consume less cellular data. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 19 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 More
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn more
Serve static assets with an efficient cache policy
43 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
5.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
3.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid enormous network payloads
Total size was 3,124 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks
11 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
65 requests • 3,124 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
3 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.
Avoid non-composited animations
2 animated elements found
Animations which are not composited can be janky and increase CLS. Learn more

Fanbox.cc Mobile SEO: 88/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
56% appropriately sized tap targets
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.

Fanbox.cc Mobile Best Practices: 87/100
Quick overview:
General
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.
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
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.
Fanbox.cc Mobile Progressive Web App: 50/100
Quick overview:
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Fanbox.cc Mobile Accessibility: 59/100
Quick overview:
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
Navigation
These are opportunities to improve keyboard navigation in your application.
The page does not contain a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
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 more.
Similar tests
www.fanbox.com
www.fanbox.net
www.fanbox.org
www.fanbox.info
www.fanbox.biz
www.fanbox.us
www.fanbox.mobi
www.anbox.cc
www.fanbox.cc
www.canbox.cc
www.fcanbox.cc
www.cfanbox.cc
www.danbox.cc
www.fdanbox.cc
www.dfanbox.cc
www.ranbox.cc
www.franbox.cc
www.rfanbox.cc
www.tanbox.cc
www.ftanbox.cc
www.tfanbox.cc
www.ganbox.cc
www.fganbox.cc
www.gfanbox.cc
www.vanbox.cc
www.fvanbox.cc
www.vfanbox.cc
www.fnbox.cc
www.fqnbox.cc
www.faqnbox.cc
www.fqanbox.cc
www.fwnbox.cc
www.fawnbox.cc
www.fwanbox.cc
www.fsnbox.cc
www.fasnbox.cc
www.fsanbox.cc
www.fznbox.cc
www.faznbox.cc
www.fzanbox.cc
www.fabox.cc
www.fabbox.cc
www.fanbbox.cc
www.fabnbox.cc
www.fahbox.cc
www.fanhbox.cc
www.fahnbox.cc
www.fajbox.cc
www.fanjbox.cc
www.fajnbox.cc
www.fambox.cc
www.fanmbox.cc
www.famnbox.cc
www.fanox.cc
www.fanvox.cc
www.fanbvox.cc
www.fanvbox.cc
www.fangox.cc
www.fanbgox.cc
www.fangbox.cc
www.fanhox.cc
www.fanbhox.cc
www.fannox.cc
www.fanbnox.cc
www.fannbox.cc
www.fanbx.cc
www.fanbix.cc
www.fanboix.cc
www.fanbiox.cc
www.fanbkx.cc
www.fanbokx.cc
www.fanbkox.cc
www.fanblx.cc
www.fanbolx.cc
www.fanblox.cc
www.fanbpx.cc
www.fanbopx.cc
www.fanbpox.cc
www.fanbo.cc
www.fanboz.cc
www.fanboxz.cc
www.fanbozx.cc
www.fanbos.cc
www.fanboxs.cc
www.fanbosx.cc
www.fanbod.cc
www.fanboxd.cc
www.fanbodx.cc
www.fanboc.cc
www.fanboxc.cc
www.fanbocx.cc
Last Tested: