Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

epolab.com

Industrial Epoxy Resin Suppliers | Epolab - Custom Epoxy Resin Solutions

Page Load Speed

8.2 sec in total

First Response

517 ms

Resources Loaded

7.3 sec

Page Rendered

395 ms

epolab.com screenshot

About Website

Visit epolab.com now to see the best up-to-date Epolab content and also check out these interesting facts you probably never knew about epolab.com

Partner with Epolab for your industrial epoxy resin needs. As leading epoxy resin suppliers, we offer a diverse selection of epoxy resins and compounds, customized to meet your specific requirements. ...

Visit epolab.com

Key Findings

We analyzed Epolab.com page load time and found that the first response time was 517 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

epolab.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value17.8 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value2,320 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value22.7 s

1/100

10%

Network Requests Diagram

epolab.com

517 ms

www.epolab.com

819 ms

bootstrap.min.css

91 ms

font-awesome.min.css

904 ms

owl.carousel.css

937 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 55% of them (41 requests) were addressed to the original Epolab.com, 12% (9 requests) were made to Rwd.gtut.com.tw and 7% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Epolab.com.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

1.0 MB

In fact, the total size of Epolab.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. Javascripts take 612.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 33.2 kB

  • Original 40.5 kB
  • After minification 30.4 kB
  • After compression 7.3 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 10.1 kB, which is 25% 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 33.2 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 21.6 kB

  • Original 388.9 kB
  • After minification 367.3 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. Epolab images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 57.7 kB

  • Original 612.3 kB
  • After minification 611.6 kB
  • After compression 554.6 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

-5%

Potential reduce by 5.1 kB

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

Requests Breakdown

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

Requests Now

71

After Optimization

18

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

Accessibility Review

epolab.com accessibility score

52

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

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

High

Page has valid source maps

SEO Factors

epolab.com SEO score

75

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

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epolab.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Epolab.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

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