Access famimo.com. famimo

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

famimo.com

2274 ms

style.css

384 ms

custom.css

350 ms

jquery.js

527 ms

jquery.selectboxes.pack.js

352 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 54% of them (65 requests) were addressed to the original Famimo.com, 17% (20 requests) were made to Static.xx.fbcdn.net and 15% (18 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Famimo.com.

Content Size

3.9 MB

After Optimization

2.2 MB

In fact, the total size of Famimo.com main page is 3.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 41.0 kB

Original 53.5 kB
After minification 49.9 kB
After compression 12.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 41.0 kB or 77% of the original size.

Image Optimization

-42%

Potential reduce by 1.5 MB

Original 3.6 MB
After minification 2.1 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Famimo needs image optimization as it can save up to 1.5 MB or 42% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 88.6 kB

Original 212.5 kB
After minification 212.3 kB
After compression 123.9 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 88.6 kB or 42% of the original size.

CSS Optimization

-48%

Potential reduce by 14.4 kB

Original 30.1 kB
After minification 30.1 kB
After compression 15.7 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Famimo.com needs all CSS files to be minified and compressed as it can save up to 14.4 kB or 48% of the original size.

Requests Now

116

After Optimization

The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Famimo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Famimo.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Famimo.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

famimo.com

Open Graph data is detected on the main page of Famimo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

famimo

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

famimo.com

style.css

custom.css

jquery.js

jquery.selectboxes.pack.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

famimo.com

style.css

custom.css

jquery.js

jquery.selectboxes.pack.js

common.js

statusChange.js

jsapi

widgets.js

userTag.js

clip.js

goods.js

socialLogin.js

pc_common.js

user.js

gpt.js

p7.js

loader.js

m_api.php

analytics.js

ee2e791ea59c8539fc9e423c18b98ec4.png

300_300_f.jpg

300_300_f.jpg

67d8ea8b4663c7f3163927513ce6f376.png

33f84a168c99353cbc3fbfe376c448c3.png

31c20be4e76cebb545dbf0a53e84587e.png

9a0f57c08ac53cf3cef7718f4c35dced.png

d788ccf20cbc3c026c22221936d0d9b1.png

480f652d446ddae71cadafd13a228c33.png

6c2d70d77352e259b67598449930b92b.png

efb83a1df52e734cdba6ccc853c5a449.png

68024252ffdfc23d4353a12a2a3e9cc1.png

15332c372e4aea2a294dea965900a63a.png

13449e967ab542bb60c39ffe3db56af8.png

a7f550a590bd70d1c603f515bd7c39d3.png

04c785eb977f75a48a710341c84e2d8d.png

300_300_f.jpg

300_300_f.png

300_300_f.jpg

300_300_f.jpg

300_300_f.jpg

300_300_f.png

300_300_f.jpg