Tools & Wizards About Us

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

antina.jp

カタログギフト、贈り物ならantina gift studio(アンティナギフトスタジオ)

Page Load Speed

25.3 sec in total

First Response

725 ms

Resources Loaded

23.1 sec

Page Rendered

1.5 sec

About Website

Welcome to antina.jp homepage info - get ready to check Antina best content for Japan right away, or after learning these important things about antina.jp

贈り物、カタログギフトの専門店アンティナ。出産祝い、結婚祝い、出産内祝い、結婚内祝いのギフトが豊富。

Visit antina.jp

Key Findings

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

Performance Metrics

antina.jp performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value27.0 s

0/100

25%

SI (Speed Index)

Value37.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value32.8 s

0/100

10%

Network Requests Diagram

antina.jp

725 ms

antina.jp

1462 ms

685 ms

gtm.js

80 ms

jquery-1.12.4.min.js

728 ms

Our browser made a total of 302 requests to load all elements on the main page. We found that 92% of them (279 requests) were addressed to the original Antina.jp, 2% (6 requests) were made to Fonts.googleapis.com and 1% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Antina.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 789.2 kB (3%)

Content Size

26.5 MB

After Optimization

25.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-90%

Potential reduce by 237.3 kB

  • Original 264.1 kB
  • After minification 195.5 kB
  • After compression 26.9 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 68.6 kB, which is 26% 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 237.3 kB or 90% of the original size.

Image Optimization

-2%

Potential reduce by 475.7 kB

  • Original 25.9 MB
  • After minification 25.4 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. Antina images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 20.2 kB

  • Original 265.6 kB
  • After minification 262.9 kB
  • After compression 245.4 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

-45%

Potential reduce by 56.1 kB

  • Original 125.5 kB
  • After minification 110.3 kB
  • After compression 69.4 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. Antina.jp needs all CSS files to be minified and compressed as it can save up to 56.1 kB or 45% of the original size.

Requests Breakdown

Number of requests can be reduced by 75 (25%)

Requests Now

295

After Optimization

220

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

antina.jp accessibility score

55

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

antina.jp best practices score

58

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

High

Page has valid source maps

SEO Factors

antina.jp SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Antina.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 Antina.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

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