Follop.co.jp Site Title

HOME | Follopコーポレート

Follop.co.jp Meta Description

「個人の価値が評価される世界を創る」をミッションとして、マイクロインフルエンサーマーケティング事業を行う「Follop(フォロップ)」のコーポレートサイトです。

Follop.co.jp Test Results

Follop.co.jp Mobile Performance: 22/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Properly size images. Potential savings of 1,993 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Remove unused JavaScript. Potential savings of 188 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Serve images in next-gen formats. Potential savings of 351 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.
Eliminate render-blocking resources. Potential savings of 1,050 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.
Enable text compression. Potential savings of 33 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Minify CSS. Potential savings of 21 KiB
Minifying CSS files can reduce network payload sizes. Learn more.
Remove unused CSS. Potential savings of 231 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 450 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 more.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Serve static assets with an efficient cache policy
9 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid enormous network payloads
Total size was 5,372 KiB
Large network payloads cost users real money and are highly correlated with long load times. 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
2.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid long main-thread tasks
14 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid chaining critical requests
59 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.
Keep request counts low and transfer sizes small
94 requests • 5,372 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.

Follop.co.jp Mobile SEO: 93/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.

Follop.co.jp Mobile Best Practices: 79/100
Quick overview:
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 servedover 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.
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.
General
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
Follop.co.jp Mobile Progressive Web App: 21/100
Quick overview:
Installable
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.
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
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 servedover 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.
PWA Optimized
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
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.
Does not provide fallback content when JavaScript is not available
Your app should display some content when JavaScript is disabled, even if it's just a warning to the user that JavaScript is required to use the app. Learn more. The page body should render some content if its scripts are not available.
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.
Fast and reliable
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Page load is not fast enough on mobile networks
Interactive at 13.7 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Follop.co.jp Mobile Accessibility: 68/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.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
Similar tests
www.follop.com
www.follop.net
www.follop.org
www.follop.info
www.follop.biz
www.follop.us
www.follop.mobi
www.ollop.co.jp
www.follop.co.jp
www.collop.co.jp
www.fcollop.co.jp
www.cfollop.co.jp
www.dollop.co.jp
www.fdollop.co.jp
www.dfollop.co.jp
www.rollop.co.jp
www.frollop.co.jp
www.rfollop.co.jp
www.tollop.co.jp
www.ftollop.co.jp
www.tfollop.co.jp
www.gollop.co.jp
www.fgollop.co.jp
www.gfollop.co.jp
www.vollop.co.jp
www.fvollop.co.jp
www.vfollop.co.jp
www.fllop.co.jp
www.fillop.co.jp
www.foillop.co.jp
www.fiollop.co.jp
www.fkllop.co.jp
www.fokllop.co.jp
www.fkollop.co.jp
www.flllop.co.jp
www.folllop.co.jp
www.flollop.co.jp
www.fpllop.co.jp
www.fopllop.co.jp
www.fpollop.co.jp
www.folop.co.jp
www.foplop.co.jp
www.folplop.co.jp
www.foolop.co.jp
www.fololop.co.jp
www.foollop.co.jp
www.foklop.co.jp
www.folklop.co.jp
www.folpop.co.jp
www.follpop.co.jp
www.foloop.co.jp
www.folloop.co.jp
www.folkop.co.jp
www.follkop.co.jp
www.follp.co.jp
www.follip.co.jp
www.folloip.co.jp
www.folliop.co.jp
www.follkp.co.jp
www.follokp.co.jp
www.folllp.co.jp
www.follolp.co.jp
www.follpp.co.jp
www.follopp.co.jp
www.follo.co.jp
www.folloo.co.jp
www.follopo.co.jp
www.follol.co.jp
www.follopl.co.jp
Last Tested: