Tools & Wizards About Us
meax.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

meax.com

Machine tooling calibration and machine measuring with MEAX

Page Load Speed

3.2 sec in total

First Response

307 ms

Resources Loaded

2.6 sec

Page Rendered

291 ms

meax.com screenshot

About Website

Click here to check amazing MEAX content. Otherwise, check out these important facts you probably never knew about meax.com

Innovative machine measuring and machine tooling calibration with a genuinely intuitive interface. MEAX - The future of machine measurement.

Visit meax.com

Key Findings

We analyzed Meax.com page load time and found that the first response time was 307 ms and then it took 2.9 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

meax.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.891

3/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

meax.com

307 ms

www.meax.com

599 ms

js

66 ms

tracking.min.js

59 ms

style.min.css

99 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 59% of them (36 requests) were addressed to the original Meax.com, 10% (6 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to T.visitorqueue.com. The less responsive or slowest element that took the longest time to load (710 ms) relates to the external source Uc.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 43.8 kB (4%)

Content Size

1.2 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Meax.com main page is 1.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 853.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 34.6 kB

  • Original 43.8 kB
  • After minification 41.2 kB
  • After compression 9.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. 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 34.6 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 6 B

  • Original 853.9 kB
  • After minification 853.9 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. MEAX images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 9.2 kB

  • Original 260.9 kB
  • After minification 260.4 kB
  • After compression 251.7 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

-0%

Potential reduce by 0 B

  • Original 59.3 kB
  • After minification 59.3 kB
  • After compression 59.3 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. Meax.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (52%)

Requests Now

50

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

meax.com

meax.com

307 ms

www.meax.com

www.meax.com

599 ms

js

js

66 ms

tracking.min.js

tracking.min.js

59 ms

style.min.css

style.min.css

99 ms

select2.min.css

select2.min.css

195 ms

beautiful-taxonomy-filters-base.min.css

beautiful-taxonomy-filters-base.min.css

283 ms

meax-public.css

meax-public.css

284 ms

style.css

style.css

287 ms

flexslider.css

flexslider.css

292 ms

jquery.min.js

jquery.min.js

389 ms

jquery-migrate.min.js

jquery-migrate.min.js

293 ms

meax-public.js

meax-public.js

379 ms

picturefill.min.js

picturefill.min.js

379 ms

select2.full.min.js

select2.full.min.js

382 ms

en.js

en.js

382 ms

beautiful-taxonomy-filters-public.js

beautiful-taxonomy-filters-public.js

447 ms

jquery.flexslider.js

jquery.flexslider.js

516 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

515 ms

script-min.js

script-min.js

515 ms

open

open

76 ms

open

open

53 ms

tracking.min.js

tracking.min.js

9 ms

open

open

59 ms

css

css

31 ms

css

css

48 ms

css

css

50 ms

sigill

sigill

710 ms

ACOEM-LOGO_Orange-vit.png

ACOEM-LOGO_Orange-vit.png

106 ms

ACOEM-LOGO-WithoutBaseline-CMYK-Bicolor.png

ACOEM-LOGO-WithoutBaseline-CMYK-Bicolor.png

104 ms

MEAX-MT30-2-cases-250x150.png

MEAX-MT30-2-cases-250x150.png

105 ms

Product-MEAX-MT20-200x200-150x150.png

Product-MEAX-MT20-200x200-150x150.png

196 ms

7-0506-03-Packing-Meax-Uni-case-4-Whats-in-the-case-Coax-200x150.png

7-0506-03-Packing-Meax-Uni-case-4-Whats-in-the-case-Coax-200x150.png

196 ms

7-0506-01-Packing-Meax-Uni-case-4-Whats-in-the-case-Level-Single-1280x960-200x150.png

7-0506-01-Packing-Meax-Uni-case-4-Whats-in-the-case-Level-Single-1280x960-200x150.png

197 ms

7-0506-02-Packing-Meax-Uni-case-4-Whats-in-the-case-Level-Dual-1280x960-200x150.png

7-0506-02-Packing-Meax-Uni-case-4-Whats-in-the-case-Level-Dual-1280x960-200x150.png

197 ms

MEAX-LEVEL-500x250.jpg

MEAX-LEVEL-500x250.jpg

189 ms

MEAX-MT30-500x250.jpg

MEAX-MT30-500x250.jpg

193 ms

MEAX-DOX-REPORT.png

MEAX-DOX-REPORT.png

194 ms

LMLR-frilagd.png

LMLR-frilagd.png

524 ms

9p8-PP_Ky7Q

9p8-PP_Ky7Q

186 ms

MEAX-PEN-Product-2.jpg

MEAX-PEN-Product-2.jpg

490 ms

MEAX-LEVEL-500x250.jpg

MEAX-LEVEL-500x250.jpg

491 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8SX21nejpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8SX21nejpw.ttf

44 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Rf21nejpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Rf21nejpw.ttf

44 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8cLx1nejpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8cLx1nejpw.ttf

52 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Yzx1nejpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Yzx1nejpw.ttf

53 ms

meax.woff

meax.woff

427 ms

MEAX-Sensor-in-holder-e1555576864604.png

MEAX-Sensor-in-holder-e1555576864604.png

654 ms

MEAX-sqareness-e1555576918366.png

MEAX-sqareness-e1555576918366.png

645 ms

MEAX-MT30.png

MEAX-MT30.png

660 ms

MEAX-LEVEL-500x250.jpg

MEAX-LEVEL-500x250.jpg

396 ms

www-player.css

www-player.css

9 ms

www-embed-player.js

www-embed-player.js

28 ms

base.js

base.js

53 ms

ad_status.js

ad_status.js

178 ms

rhvPcg7UJyL1sAnNU7zDxBIVtgC_UiLHJg5Qt6Nsf8o.js

rhvPcg7UJyL1sAnNU7zDxBIVtgC_UiLHJg5Qt6Nsf8o.js

130 ms

embed.js

embed.js

67 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

19 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

22 ms

Create

Create

89 ms

id

id

86 ms

Accessibility Review

meax.com accessibility score

82

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

meax.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

meax.com SEO score

83

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

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Meax.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Meax.com 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

meax.com

Open Graph data is detected on the main page of MEAX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: