Tools & Wizards About Us
meikai.com.au screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

Page Load Speed

3.4 sec in total

First Response

991 ms

Resources Loaded

2.1 sec

Page Rendered

328 ms

meikai.com.au screenshot

About Website

Click here to check amazing Meikai content. Otherwise, check out these important facts you probably never knew about meikai.com.au

Visit meikai.com.au

Key Findings

We analyzed Meikai.com.au page load time and found that the first response time was 991 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.

Performance Metrics

meikai.com.au performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value0.8 s

100/100

10%

Network Requests Diagram

meikai.com.au

991 ms

menu.css

404 ms

chrome.php

407 ms

e021_04.png

434 ms

e021_06.png

435 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that all of those requests were addressed to Meikai.com.au and no external sources were called. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Meikai.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 16.5 kB (19%)

Content Size

86.1 kB

After Optimization

69.5 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Meikai.com.au main page is 86.1 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. Only 5% of websites need less resources to load. Images take 66.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 15.6 kB

  • Original 19.0 kB
  • After minification 16.1 kB
  • After compression 3.4 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 2.9 kB, which is 15% 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 15.6 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 429 B

  • Original 66.3 kB
  • After minification 65.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. Meikai images are well optimized though.

CSS Optimization

-61%

Potential reduce by 498 B

  • Original 812 B
  • After minification 656 B
  • After compression 314 B

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. Meikai.com.au needs all CSS files to be minified and compressed as it can save up to 498 B or 61% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

13

After Optimization

13

  • AJAX
  • Images
  • CSS

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Meikai. According to our analytics all requests are already optimized.

Network Requests Diagram

meikai.com.au

meikai.com.au

991 ms

menu.css

menu.css

404 ms

chrome.php

chrome.php

407 ms

e021_04.png

e021_04.png

434 ms

e021_06.png

e021_06.png

435 ms

e021_07.png

e021_07.png

434 ms

e021_10.png

e021_10.png

559 ms

e021_13.png

e021_13.png

808 ms

e021_17.png

e021_17.png

804 ms

e021_15.png

e021_15.png

831 ms

e021_09.png

e021_09.png

1242 ms

spacer.gif

spacer.gif

855 ms

meikai.jpg

meikai.jpg

967 ms

e021_21.png

e021_21.png

1072 ms

Accessibility Review

meikai.com.au accessibility score

56

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

meikai.com.au best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

meikai.com.au SEO score

67

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Meikai.com.au can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Meikai.com.au main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

meikai.com.au

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