Tools & Wizards About Us
matismart.com screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

matismart.com

Focus on Smart AIoT Electrics Solutions | Matismart

Page Load Speed

9.9 sec in total

First Response

658 ms

Resources Loaded

8.8 sec

Page Rendered

447 ms

matismart.com screenshot

About Website

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

Matismart is a manufacturer with years of R&D and production focused on smart AIoT electricity solutions and offering smart energy hardware and software.

Visit matismart.com

Key Findings

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

Performance Metrics

matismart.com performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.819

4/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

matismart.com

658 ms

www.matismart.com

1317 ms

swiper.min.css

431 ms

default.css

1067 ms

jquery-2.2.4.min.js

1284 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 97% of them (114 requests) were addressed to the original Matismart.com, 2% (2 requests) were made to Googletagmanager.com and 1% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Matismart.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 975.6 kB (31%)

Content Size

3.1 MB

After Optimization

2.2 MB

  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-15%

Potential reduce by 336.3 kB

  • Original 2.3 MB
  • After minification 1.9 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. Obviously, Matismart needs image optimization as it can save up to 336.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 556.6 kB

  • Original 758.5 kB
  • After minification 754.2 kB
  • After compression 201.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 556.6 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 82.6 kB

  • Original 97.2 kB
  • After minification 79.6 kB
  • After compression 14.6 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. Matismart.com needs all CSS files to be minified and compressed as it can save up to 82.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (7%)

Requests Now

114

After Optimization

106

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

matismart.com

matismart.com

658 ms

www.matismart.com

www.matismart.com

1317 ms

swiper.min.css

swiper.min.css

431 ms

default.css

default.css

1067 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

1284 ms

layer.js

layer.js

649 ms

js

js

44 ms

js

js

92 ms

public.js

public.js

658 ms

swiper.min.js

swiper.min.js

1099 ms

three.min.js

three.min.js

1957 ms

Detector.js

Detector.js

655 ms

layer.css

layer.css

220 ms

fbevents.js

fbevents.js

78 ms

logo1.png

logo1.png

218 ms

logo2.png

logo2.png

220 ms

hdico1.png

hdico1.png

219 ms

hdico1_.png

hdico1_.png

224 ms

hdico2.png

hdico2.png

221 ms

rg3.png

rg3.png

437 ms

youtube.png

youtube.png

436 ms

rg1.png

rg1.png

438 ms

rgico3.png

rgico3.png

439 ms

20191212143511718.jpg

20191212143511718.jpg

444 ms

rgico5.png

rgico5.png

679 ms

20230418104313291.jpg

20230418104313291.jpg

680 ms

bnyq1.png

bnyq1.png

680 ms

bnyq2.png

bnyq2.png

681 ms

bnyq4.png

bnyq4.png

681 ms

bnyq5.png

bnyq5.png

866 ms

bnyq6.png

bnyq6.png

871 ms

bnsc1.png

bnsc1.png

873 ms

bnsc2.png

bnsc2.png

873 ms

bnsc3.png

bnsc3.png

879 ms

bnsc4.png

bnsc4.png

887 ms

bnsc5.png

bnsc5.png

1085 ms

bnsc6.png

bnsc6.png

1088 ms

bnsc7.png

bnsc7.png

1090 ms

bnsc8.png

bnsc8.png

1092 ms

20230418104847561.jpg

20230418104847561.jpg

1314 ms

20230418105041565.jpg

20230418105041565.jpg

1110 ms

20230418105107389.jpg

20230418105107389.jpg

1307 ms

20230418105137667.jpg

20230418105137667.jpg

1307 ms

left.png

left.png

1307 ms

clxlu1.png

clxlu1.png

1309 ms

zuotu1.png

zuotu1.png

1331 ms

youtu1.png

youtu1.png

1523 ms

youti1.png

youti1.png

1531 ms

jianz8.png

jianz8.png

1467 ms

3A9EE5_0_0.woff

3A9EE5_0_0.woff

1311 ms

jianz9.png

jianz9.png

1323 ms

jianz10.png

jianz10.png

1336 ms

jianz7.png

jianz7.png

1524 ms

jianz5.png

jianz5.png

1520 ms

jianz5_.png

jianz5_.png

1312 ms

jianz6.png

jianz6.png

1315 ms

jianz1.png

jianz1.png

1319 ms

jianz4.png

jianz4.png

1337 ms

jianz2.png

jianz2.png

1514 ms

jianz3.png

jianz3.png

1282 ms

yun1.png

yun1.png

1284 ms

yun2.png

yun2.png

1293 ms

huoc1.png

huoc1.png

1296 ms

clol1.png

clol1.png

1317 ms

clol2.png

clol2.png

1512 ms

clol3.png

clol3.png

1328 ms

clol4.png

clol4.png

1325 ms

clol5.png

clol5.png

1324 ms

clol6.png

clol6.png

1324 ms

clol7.png

clol7.png

1340 ms

clol8.png

clol8.png

1523 ms

clor1.png

clor1.png

1327 ms

clor2.png

clor2.png

1324 ms

clor3.png

clor3.png

1327 ms

clor4.png

clor4.png

1325 ms

clor5.png

clor5.png

1330 ms

clor6.png

clor6.png

1322 ms

bg3.jpg

bg3.jpg

1324 ms

tabico1.png

tabico1.png

1323 ms

20191012175301134.png

20191012175301134.png

1544 ms

20230417151036349.png

20230417151036349.png

1322 ms

20230411092809253.jpg

20230411092809253.jpg

1329 ms

20230202093520954.png

20230202093520954.png

1322 ms

20230417153752127.png

20230417153752127.png

1323 ms

20240313155034883.jpg

20240313155034883.jpg

1318 ms

20230131084529888.png

20230131084529888.png

1321 ms

20230414105154188.png

20230414105154188.png

1346 ms

20210510103402128.png

20210510103402128.png

1508 ms

20230417144531570.png

20230417144531570.png

3004 ms

20230615164228238.png

20230615164228238.png

3006 ms

20230417160030492.png

20230417160030492.png

3244 ms

20230417161937850.png

20230417161937850.png

3031 ms

20230414103256743.png

20230414103256743.png

3074 ms

20230417162557328.png

20230417162557328.png

1504 ms

2023041716354719.png

2023041716354719.png

1540 ms

20241122144216699.png

20241122144216699.png

1755 ms

20241122103203615.png

20241122103203615.png

1969 ms

left11.png

left11.png

2178 ms

right.png

right.png

2391 ms

2023041813371872.jpg

2023041813371872.jpg

2584 ms

2023041814182449.jpg

2023041814182449.jpg

2605 ms

2023041813324621.png

2023041813324621.png

2775 ms

casimg1.jpg

casimg1.jpg

2775 ms

bg1.jpg

bg1.jpg

2808 ms

caico1.png

caico1.png

2820 ms

more1.png

more1.png

2831 ms

more2.png

more2.png

2782 ms

map_bg.png

map_bg.png

2998 ms

map_line.png

map_line.png

2797 ms

line1.png

line1.png

2809 ms

20230418113517359.jpg

20230418113517359.jpg

2818 ms

20230418113635160.jpg

20230418113635160.jpg

2831 ms

20230418113812547.jpg

20230418113812547.jpg

2783 ms

20191209181029247.jpg

20191209181029247.jpg

2802 ms

hdico4.png

hdico4.png

2915 ms

close1.png

close1.png

2907 ms

service_icon8.png

service_icon8.png

2884 ms

Accessibility Review

matismart.com accessibility score

75

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

Links do not have a discernible name

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

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

Displays images with incorrect aspect ratio

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

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

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

matismart.com

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