Tools & Wizards About Us
meidaisha.co.jp screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

meidaisha.co.jp

ジモト就職なら名大社～愛知・岐阜・三重を愛するすべての人へ～｜株式会社名大社

Page Load Speed

4.4 sec in total

First Response

819 ms

Resources Loaded

3.3 sec

Page Rendered

323 ms

meidaisha.co.jp screenshot

About Website

Click here to check amazing Meidaisha content for Japan. Otherwise, check out these important facts you probably never knew about meidaisha.co.jp

この街にあるたくさんの優良企業と、この街で働きたいあなたをサポート。名大社はジモト就職＆ジモト転職を応援します。

Visit meidaisha.co.jp

Key Findings

We analyzed Meidaisha.co.jp page load time and found that the first response time was 819 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

meidaisha.co.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.211

59/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

meidaisha.co.jp

819 ms

jquery.bxslider.css

338 ms

index.css

341 ms

index_sp.css

366 ms

jquery.min.js

37 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 63% of them (61 requests) were addressed to the original Meidaisha.co.jp, 18% (17 requests) were made to Maps.google.com and 6% (6 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Meidaisha.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 584.7 kB (24%)

Content Size

2.5 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Meidaisha.co.jp main page is 2.5 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. 55% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 43.8 kB

  • Original 52.1 kB
  • After minification 47.6 kB
  • After compression 8.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 43.8 kB or 84% of the original size.

Image Optimization

-10%

Potential reduce by 181.9 kB

  • Original 1.9 MB
  • After minification 1.7 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. Meidaisha images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 334.4 kB

  • Original 516.9 kB
  • After minification 514.2 kB
  • After compression 182.6 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 334.4 kB or 65% of the original size.

CSS Optimization

-81%

Potential reduce by 24.6 kB

  • Original 30.4 kB
  • After minification 21.8 kB
  • After compression 5.8 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. Meidaisha.co.jp needs all CSS files to be minified and compressed as it can save up to 24.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (21%)

Requests Now

92

After Optimization

73

  • Images
  • JavaScript
  • CSS

The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Meidaisha. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

meidaisha.co.jp

meidaisha.co.jp

819 ms

jquery.bxslider.css

jquery.bxslider.css

338 ms

index.css

index.css

341 ms

index_sp.css

index_sp.css

366 ms

jquery.min.js

jquery.min.js

37 ms

js

js

84 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

396 ms

scrollsmoothly.js

scrollsmoothly.js

393 ms

header_logo.png

header_logo.png

226 ms

tab_active_pc.png

tab_active_pc.png

226 ms

tab_active_sp.png

tab_active_sp.png

344 ms

tab_inactive_pc.png

tab_inactive_pc.png

226 ms

tab_inactive_sp.png

tab_inactive_sp.png

224 ms

g_navi01_off.png

g_navi01_off.png

224 ms

g_navi02_off.png

g_navi02_off.png

415 ms

g_navi03_off.png

g_navi03_off.png

418 ms

g_navi04_off.png

g_navi04_off.png

417 ms

g_navi05_off.png

g_navi05_off.png

415 ms

g_navi06_off.png

g_navi06_off.png

388 ms

25_image.png

25_image.png

1008 ms

1_image.jpg

1_image.jpg

1393 ms

19_image.png

19_image.png

1167 ms

h_background.gif

h_background.gif

598 ms

h_info_shinsotsu.png

h_info_shinsotsu.png

594 ms

h_event_for_student.png

h_event_for_student.png

606 ms

icon_category_7.png

icon_category_7.png

774 ms

20_image.png

20_image.png

783 ms

icon_date.png

icon_date.png

797 ms

icon_place.png

icon_place.png

955 ms

12_image.png

12_image.png

1150 ms

21_image.png

21_image.png

1363 ms

h_navi2017.png

h_navi2017.png

1136 ms

banner_navi2017.png

banner_navi2017.png

1176 ms

h_navi2016.png

h_navi2016.png

1316 ms

banner_navi2016.png

banner_navi2016.png

1519 ms

h_eventpage.png

h_eventpage.png

1356 ms

shin_event_ban.png

shin_event_ban.png

1346 ms

h_shin_seminar.png

h_shin_seminar.png

1497 ms

shin_seminar_ban.png

shin_seminar_ban.png

1516 ms

h_for_chuto.png

h_for_chuto.png

1544 ms

h_event_for_mosociety.png

h_event_for_mosociety.png

1553 ms

icon_category_3.png

icon_category_3.png

1558 ms

icon_category_2.png

icon_category_2.png

1677 ms

icon_category_5.png

icon_category_5.png

1661 ms

analytics.js

analytics.js

25 ms

common.js

common.js

27 ms

map.js

map.js

42 ms

util.js

util.js

90 ms

marker.js

marker.js

89 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

167 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

248 ms

collect

collect

69 ms

onion.js

onion.js

56 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

102 ms

stats.js

stats.js

36 ms

controls.js

controls.js

34 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

115 ms

transparent.png

transparent.png

128 ms

css

css

93 ms

google4.png

google4.png

96 ms

mapcnt6.png

mapcnt6.png

126 ms

sv5.png

sv5.png

126 ms

spotlight-poi.png

spotlight-poi.png

124 ms

15_image.png

15_image.png

1485 ms

1_image.png

1_image.png

1516 ms

ban_seminar.png

ban_seminar.png

1524 ms

ban_agent.jpg

ban_agent.jpg

1508 ms

ban_radio.png

ban_radio.png

1817 ms

vt

vt

74 ms

vt

vt

99 ms

vt

vt

90 ms

vt

vt

91 ms

vt

vt

111 ms

vt

vt

78 ms

vt

vt

133 ms

vt

vt

177 ms

vt

vt

157 ms

vt

vt

158 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

149 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

188 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

223 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

223 ms

ban_presidentblog.png

ban_presidentblog.png

1515 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

188 ms

ban_staffblog.png

ban_staffblog.png

1505 ms

ban_twitter.png

ban_twitter.png

1487 ms

ban_furusato.png

ban_furusato.png

1515 ms

ban_radio_sp.png

ban_radio_sp.png

1522 ms

ban_sp_twitter.png

ban_sp_twitter.png

1608 ms

ban_sp_presidentblog.png

ban_sp_presidentblog.png

1483 ms

ban_sp_staffblog.png

ban_sp_staffblog.png

1471 ms

footer_logo.png

footer_logo.png

1513 ms

introduction_ban_off.png

introduction_ban_off.png

1355 ms

ico_arrow_b.gif

ico_arrow_b.gif

1410 ms

ico_arrow_s.gif

ico_arrow_s.gif

1426 ms

bx_loader.gif

bx_loader.gif

1281 ms

controls.png

controls.png

1249 ms

Accessibility Review

meidaisha.co.jp accessibility score

83

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Internationalization and localization

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

Impact

Issue

High

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

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

High

Links do not have a discernible name

Best Practices

meidaisha.co.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

meidaisha.co.jp SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

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 Meidaisha.co.jp 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 Meidaisha.co.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.

Social Sharing Optimization

meidaisha.co.jp

Open Graph description is not detected on the main page of Meidaisha. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: