Tools & Wizards About Us
megagasket.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

megagasket.com

MEGA ＆ SuperSEAL

Page Load Speed

3.5 sec in total

First Response

291 ms

Resources Loaded

3 sec

Page Rendered

251 ms

megagasket.com screenshot

About Website

Welcome to megagasket.com homepage info - get ready to check MEGA Gasket best content right away, or after learning these important things about megagasket.com

We offer high-quality made-in-Taiwan gaskets to fulfilling the needs of requirements.

Visit megagasket.com

Key Findings

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

megagasket.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.104

88/100

15%

TTI (Time to Interactive)

Value6.7 s

57/100

10%

Network Requests Diagram

291 ms

gtm.js

65 ms

content.css

244 ms

bootstrap.min.css

339 ms

font-awesome.min.css

349 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 82% of them (37 requests) were addressed to the original Megagasket.com, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Megagasket.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 288.8 kB (10%)

Content Size

3.0 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Megagasket.com main page is 3.0 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. 40% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 33.5 kB

  • Original 42.4 kB
  • After minification 40.5 kB
  • After compression 8.8 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 33.5 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 255.2 kB

  • Original 2.9 MB
  • After minification 2.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. MEGA Gasket images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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.

Requests Breakdown

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

Requests Now

41

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

291 ms

gtm.js

gtm.js

65 ms

content.css

content.css

244 ms

bootstrap.min.css

bootstrap.min.css

339 ms

font-awesome.min.css

font-awesome.min.css

349 ms

fa-v4-shims.css

fa-v4-shims.css

295 ms

animated.css

animated.css

39 ms

template.css

template.css

298 ms

default.css

default.css

51 ms

template.css

template.css

90 ms

jquery.min.js

jquery.min.js

403 ms

jquery-noconflict.js

jquery-noconflict.js

495 ms

jquery-migrate.min.js

jquery-migrate.min.js

307 ms

caption.js

caption.js

569 ms

popper.min.js

popper.min.js

546 ms

bootstrap.min.js

bootstrap.min.js

582 ms

main.js

main.js

616 ms

custom.js

custom.js

434 ms

vue.js

vue.js

44 ms

sweetalert.min.js

sweetalert.min.js

50 ms

inquiry.js

inquiry.js

441 ms

analytics.js

analytics.js

24 ms

collect

collect

13 ms

js

js

48 ms

css

css

31 ms

logo@2x.png

logo@2x.png

283 ms

bg-welcome.jpeg

bg-welcome.jpeg

656 ms

logo-mega.png

logo-mega.png

318 ms

logo-superseal.png

logo-superseal.png

344 ms

made-in-taiwan-logo.png

made-in-taiwan-logo.png

505 ms

mit-button.png

mit-button.png

337 ms

standard-mega.png

standard-mega.png

548 ms

Have_signs_of_blown_head_gasket01.jpg

Have_signs_of_blown_head_gasket01.jpg

707 ms

bg-slide1.jpg

bg-slide1.jpg

870 ms

%E6%96%87%E6%A1%88%E5%9C%96%E7%89%87.png

%E6%96%87%E6%A1%88%E5%9C%96%E7%89%87.png

934 ms

damir-kopezhanov-Z5tXjpTqwR8-unsplash-02_thumbnail.jpg

damir-kopezhanov-Z5tXjpTqwR8-unsplash-02_thumbnail.jpg

967 ms

Have%20signs%20of%20blown%20head%20gasket01_thumbnail.png

Have%20signs%20of%20blown%20head%20gasket01_thumbnail.png

1110 ms

Graphite%20Gasket_thumbnail.jpg

Graphite%20Gasket_thumbnail.jpg

1112 ms

Know_more_about_intake_manifold_gasket-2-01-01.jpg

Know_more_about_intake_manifold_gasket-2-01-01.jpg

1203 ms

motor-768750_1280_thumbnail.jpg

motor-768750_1280_thumbnail.jpg

1348 ms

Gasket%20Material%20Types%20For%20Gasoline%20And%20Gasket%20Selection%20Guide_thumbnail.png

Gasket%20Material%20Types%20For%20Gasoline%20And%20Gasket%20Selection%20Guide_thumbnail.png

1544 ms

logo-footer@2x.png

logo-footer@2x.png

1298 ms

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz76CyzC1EskSyqNXrqg.ttf

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz76CyzC1EskSyqNXrqg.ttf

71 ms

fa-solid-900.woff

fa-solid-900.woff

1597 ms

fa-regular-400.woff

fa-regular-400.woff

1454 ms

Accessibility Review

megagasket.com accessibility score

88

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

Links do not have a discernible name

Best Practices

megagasket.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

megagasket.com SEO score

86

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

megagasket.com

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