4.3 sec in total
866 ms
3.1 sec
319 ms
Click here to check amazing Meet I content for Japan. Otherwise, check out these important facts you probably never knew about meet-i.com
meet i [ミートアイ]はiPhoneユーザーやスマホユーザーの為の人気アプリ/気になるニュース/最新のスマートフォン情報/ガジェット情報他をお届けします!
Visit meet-i.comWe analyzed Meet-i.com page load time and found that the first response time was 866 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
meet-i.com performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value6.6 s
8/100
25%
Value13.4 s
2/100
10%
Value2,250 ms
6/100
30%
Value0.08
94/100
15%
Value20.0 s
2/100
10%
866 ms
332 ms
492 ms
333 ms
667 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 26% of them (23 requests) were addressed to the original Meet-i.com, 45% (39 requests) were made to I.meet-i.com and 9% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source I.meet-i.com.
Page size can be reduced by 419.3 kB (16%)
2.6 MB
2.2 MB
In fact, the total size of Meet-i.com main page is 2.6 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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 63.2 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 63.2 kB or 80% of the original size.
Potential reduce by 108.0 kB
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. Meet I images are well optimized though.
Potential reduce by 223.0 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 223.0 kB or 50% of the original size.
Potential reduce by 25.1 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. Meet-i.com needs all CSS files to be minified and compressed as it can save up to 25.1 kB or 67% of the original size.
Number of requests can be reduced by 28 (34%)
83
55
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Meet I. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
meet-i.com
866 ms
reset.css
332 ms
style.css
492 ms
jquery.bxslider.css
333 ms
jquery-1.10.1.js
667 ms
common.js
334 ms
heightLine.js
495 ms
jquery.bxslider.js
821 ms
jquery.ellipsis.js
498 ms
jsapi
17 ms
sh.adingo.jp
346 ms
loader.js
18 ms
sh.adingo.jp
349 ms
sh.adingo.jp
200 ms
sh.adingo.jp
355 ms
iPhone11pro_6502.jpg
1021 ms
applewatchseries5_650.jpg
855 ms
ios13.jpg
864 ms
%E3%82%A4%E3%83%A1%E3%83%BC%E3%82%B8-8.jpeg
1026 ms
iPhone11_6502.jpg
869 ms
appleevent_650-1.jpg
682 ms
ios1741_650.jpg
687 ms
M3MacBookair_650.jpg
856 ms
peekperformance_0308_03.jpg
695 ms
pokemoncard_650-2.jpg
1024 ms
ios173_650.jpg
693 ms
AllMemberKeyVisual_650.jpg
1181 ms
AnkerSoundcoreH30i_650.jpeg
1185 ms
applevisionpro_650.jpeg
864 ms
amazon_0103_650.jpeg
1030 ms
teiban300_7.png
1024 ms
applepaymatome300100.jpg
1029 ms
rightsidebanner_urazawa.jpg
1357 ms
ios17_140.png
1193 ms
krk02sm_thumb.png
1197 ms
kidokupooo655NN.png
1199 ms
pigmenticon.png
1346 ms
watchos10_140.png
1351 ms
jewelpetthum.png
1360 ms
amazon-3.png
1364 ms
pokemongoicon_01.png
1367 ms
googleicon1.png
1514 ms
wwdc22_140.jpg
1520 ms
icon_01699.png
1523 ms
famimaoden_140.png
1527 ms
teiban140.png
1531 ms
applemusic140014.png
1535 ms
Non-notification-Denial-thumb.png
1680 ms
iphone-maintenance-thumb.jpg
1687 ms
uwaraza_140.png
1695 ms
linejyojyo_new.png
1698 ms
logo.png
191 ms
title-pickup.png
191 ms
title-newarticle.png
182 ms
title-follow.png
191 ms
btn-rss.png
182 ms
btn-twitter.png
191 ms
btn-facebook.png
346 ms
title-popular.png
346 ms
analytics.js
11 ms
i.adingo.jp
691 ms
sdk.js
51 ms
icon-jenre-news.png
346 ms
icon-menuarea-twitter.png
348 ms
icon-accent.png
349 ms
icon-jenre-app.png
346 ms
cse.js
97 ms
collect
85 ms
i.adingo.jp
697 ms
i.adingo.jp
690 ms
sdk.js
68 ms
i.adingo.jp
690 ms
bx_loader.gif
627 ms
arrows.png
623 ms
collect
178 ms
js
120 ms
cse_element__ja.js
46 ms
default+ja.css
90 ms
default.css
92 ms
async-ads.js
96 ms
branding.png
20 ms
clear.png
14 ms
nav_logo114.png
15 ms
ga-audiences
66 ms
famiyoko_140.jpg
1022 ms
%E5%90%8D%E7%A7%B0%E6%9C%AA%E8%A8%AD%E5%AE%9A2.png
1020 ms
iPhone11pro_6502.jpg
491 ms
meet-i.com accessibility score
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.
Impact
Issue
<frame> or <iframe> elements do not have a title
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
meet-i.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
meet-i.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Meet-i.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Meet-i.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.
meet-i.com
Open Graph data is detected on the main page of Meet I. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: