Tools & Wizards About Us
ooatari.jp screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

ooatari.jp

大あたり.jp　：当たる懸賞サイト。一括投稿やスピードくじ作成サービスも提供。

Page Load Speed

4.7 sec in total

First Response

1.5 sec

Resources Loaded

3 sec

Page Rendered

176 ms

ooatari.jp screenshot

About Website

Click here to check amazing Ooatari content. Otherwise, check out these important facts you probably never knew about ooatari.jp

スピードくじ満載の良く当たる懸賞サイト。懸賞情報の一括投稿やスピードくじ懸賞作成サービスも。

Visit ooatari.jp

Key Findings

We analyzed Ooatari.jp page load time and found that the first response time was 1.5 sec and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ooatari.jp performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value3.9 s

89/100

10%

Network Requests Diagram

ooatari.jp

1525 ms

top.css

334 ms

common.css

339 ms

487 ms

h_search.gif

385 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 84% of them (43 requests) were addressed to the original Ooatari.jp, 6% (3 requests) were made to Image.j-a-net.jp and 6% (3 requests) were made to Draft.j-a-net.jp. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Ooatari.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 22.9 kB (43%)

Content Size

52.6 kB

After Optimization

29.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ooatari.jp main page is 52.6 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. 20% of websites need less resources to load. HTML takes 17.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 13.5 kB

  • Original 17.6 kB
  • After minification 14.2 kB
  • After compression 4.1 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. This page needs HTML code to be minified as it can gain 3.4 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 13.5 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 329 B

  • Original 6.0 kB
  • After minification 5.7 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. Ooatari images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-76%

Potential reduce by 9.0 kB

  • Original 11.9 kB
  • After minification 9.8 kB
  • After compression 2.9 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. Ooatari.jp needs all CSS files to be minified and compressed as it can save up to 9.0 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (15%)

Requests Now

47

After Optimization

40

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ooatari.jp

ooatari.jp

1525 ms

top.css

top.css

334 ms

common.css

common.css

339 ms

487 ms

h_search.gif

h_search.gif

385 ms

entry

entry

238 ms

anq_a.gif

anq_a.gif

332 ms

anq_b.gif

anq_b.gif

342 ms

ml_text.gif

ml_text.gif

346 ms

ml_email.gif

ml_email.gif

363 ms

331 ms

348 ms

0858df8c5a.gif

0858df8c5a.gif

363 ms

ga.js

ga.js

38 ms

bg.gif

bg.gif

238 ms

sitetitle.gif

sitetitle.gif

316 ms

arrow01.gif

arrow01.gif

331 ms

topmenu.gif

topmenu.gif

334 ms

btn_search.gif

btn_search.gif

364 ms

attention_bg.gif

attention_bg.gif

364 ms

titlebar_feature.gif

titlebar_feature.gif

426 ms

titlebar_sp.gif

titlebar_sp.gif

482 ms

bar_line01.gif

bar_line01.gif

511 ms

sp_tit01.gif

sp_tit01.gif

511 ms

arrow02.gif

arrow02.gif

545 ms

sp_tit02.gif

sp_tit02.gif

546 ms

sp_tit03.gif

sp_tit03.gif

614 ms

bar_line02.gif

bar_line02.gif

647 ms

sp_tit04.gif

sp_tit04.gif

682 ms

sp_tit05.gif

sp_tit05.gif

683 ms

sp_tit06.gif

sp_tit06.gif

728 ms

bar_line03.gif

bar_line03.gif

728 ms

sp_tit07.gif

sp_tit07.gif

801 ms

sp_tit08.gif

sp_tit08.gif

811 ms

sp_tit09.gif

sp_tit09.gif

852 ms

titlebar_recommend.gif

titlebar_recommend.gif

853 ms

titlebar_category.gif

titlebar_category.gif

909 ms

titlebar_news.gif

titlebar_news.gif

910 ms

which_under.gif

which_under.gif

990 ms

titlebar_which.gif

titlebar_which.gif

979 ms

btn_vote.gif

btn_vote.gif

1026 ms

titlebar_bet.gif

titlebar_bet.gif

1027 ms

titlebar_mlmagazine.gif

titlebar_mlmagazine.gif

1066 ms

__utm.gif

__utm.gif

13 ms

btn_enter.gif

btn_enter.gif

1042 ms

titlebar_inform.gif

titlebar_inform.gif

1095 ms

59985.gif

59985.gif

1144 ms

titlebar_entry.gif

titlebar_entry.gif

1034 ms

68661.gif

68661.gif

1150 ms

bar_beigedot.gif

bar_beigedot.gif

1043 ms

418592.gif

418592.gif

1053 ms

Accessibility Review

ooatari.jp accessibility score

79

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

ooatari.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

ooatari.jp SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ooatari.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 Ooatari.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

ooatari.jp

Open Graph description is not detected on the main page of Ooatari. 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: