3.1 sec in total
778 ms
2 sec
329 ms
Welcome to mei2.jp homepage info - get ready to check Mei 2 best content for Japan right away, or after learning these important things about mei2.jp
赤ちゃんの名づけに迷ったら?赤ちゃんの名前の候補を相性の良い画数別に表示する、命名お手伝いサイト
Visit mei2.jpWe analyzed Mei2.jp page load time and found that the first response time was 778 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
mei2.jp performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value4.2 s
44/100
25%
Value6.1 s
45/100
10%
Value1,240 ms
19/100
30%
Value0.13
82/100
15%
Value10.0 s
27/100
10%
778 ms
8 ms
648 ms
14 ms
69 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 16% of them (9 requests) were addressed to the original Mei2.jp, 18% (10 requests) were made to Plugins.mixi.jp and 9% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (876 ms) belongs to the original domain Mei2.jp.
Page size can be reduced by 411.0 kB (57%)
718.0 kB
306.9 kB
In fact, the total size of Mei2.jp main page is 718.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 522.7 kB which makes up the majority of the site volume.
Potential reduce by 27.7 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 27.7 kB or 72% of the original size.
Potential reduce by 7.8 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. Mei 2 images are well optimized though.
Potential reduce by 351.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 351.0 kB or 67% of the original size.
Potential reduce by 24.6 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. Mei2.jp needs all CSS files to be minified and compressed as it can save up to 24.6 kB or 84% of the original size.
Number of requests can be reduced by 28 (52%)
54
26
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mei 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
mei2.jp
778 ms
ga.js
8 ms
tab1.png
648 ms
__utm.gif
14 ms
all.js
69 ms
share.js
297 ms
bg_top.jpg
876 ms
button_top.gif
383 ms
bg_info.jpg
624 ms
widgets.js
6 ms
kakusu_setsumei.gif
380 ms
147 ms
xd_arbiter.php
89 ms
xd_arbiter.php
142 ms
show_ads.js
38 ms
button_to_top.gif
258 ms
ad_cruri.png
452 ms
share_button.html
344 ms
favorite.pl
374 ms
bg_fin_y.jpg
302 ms
ca-pub-3750681115872866.js
211 ms
zrt_lookup.html
236 ms
show_ads_impl.js
88 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
155 ms
ads
281 ms
osd.js
38 ms
ads
306 ms
bt_check_2.png
378 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
27 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
40 ms
mixi_check_entry.css
49 ms
errorreport.production.js
331 ms
json.js
335 ms
underscore-string-1.3.3-2.0.0-compress.js
334 ms
namespace-brook-compress.js
345 ms
prototype-effects-1.6.1-1.8.3-compress.js
446 ms
mixi.js
341 ms
plugins.js
149 ms
favorite.production.js
585 ms
jquery-1.7.1.min-noconflict-compress.js
736 ms
like.php
81 ms
8i5wLKr4CIi.js
142 ms
LVx-xkvaJ0b.png
155 ms
m_js_controller.js
34 ms
abg.js
48 ms
favicon
68 ms
googlelogo_color_112x36dp.png
66 ms
nessie_icon_tiamat_white.png
53 ms
s
42 ms
x_button_blue2.png
31 ms
jot.html
25 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
3 ms
analytics.js
8 ms
comment001.gif
7 ms
favorite_button003-.png
8 ms
comment_content_top001.gif
4 ms
mei2.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
mei2.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
mei2.jp SEO score
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 Mei2.jp 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 Mei2.jp 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.
mei2.jp
Open Graph data is detected on the main page of Mei 2. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: