Tools & Wizards About Us
moskiller.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

moskiller.com

Moskiller, Solar insect trap,Mosquito Killer,Mosquito Trap,solar trap

Page Load Speed

5.6 sec in total

First Response

1.3 sec

Resources Loaded

4.1 sec

Page Rendered

244 ms

moskiller.com screenshot

About Website

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

QM Solar insect trap,Mosquito Killer,Mosquito Trap

Visit moskiller.com

Key Findings

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

Performance Metrics

moskiller.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

moskiller.com

1328 ms

style.css

1982 ms

font-awesome.css

267 ms

jquery-1.9.min.js

1534 ms

pixelunion-options-select.js

887 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 71% of them (25 requests) were addressed to the original Moskiller.com, 23% (8 requests) were made to Cdn.shopify.com and 6% (2 requests) were made to Cdn.staticfile.org. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Moskiller.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 382.2 kB (61%)

Content Size

628.8 kB

After Optimization

246.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Moskiller.com main page is 628.8 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. 15% of websites need less resources to load. Javascripts take 209.2 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 47.2 kB

  • Original 54.1 kB
  • After minification 46.4 kB
  • After compression 6.9 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 7.7 kB, which is 14% 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 47.2 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 9.1 kB

  • Original 166.9 kB
  • After minification 157.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. Moskiller images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 150.6 kB

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

CSS Optimization

-88%

Potential reduce by 175.3 kB

  • Original 198.6 kB
  • After minification 119.5 kB
  • After compression 23.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. Moskiller.com needs all CSS files to be minified and compressed as it can save up to 175.3 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (15%)

Requests Now

27

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

moskiller.com

moskiller.com

1328 ms

style.css

style.css

1982 ms

font-awesome.css

font-awesome.css

267 ms

jquery-1.9.min.js

jquery-1.9.min.js

1534 ms

pixelunion-options-select.js

pixelunion-options-select.js

887 ms

plugins.js

plugins.js

436 ms

site.js

site.js

689 ms

main-sprite.png

main-sprite.png

61 ms

MOSKILLERlogo.gif

MOSKILLERlogo.gif

241 ms

Fan_P_FL_1024x1024.jpg

Fan_P_FL_1024x1024.jpg

222 ms

Fan_P_FL_small.jpg

Fan_P_FL_small.jpg

231 ms

Fan_P_Wall_small.jpg

Fan_P_Wall_small.jpg

233 ms

Fan_P_Angle_small.jpg

Fan_P_Angle_small.jpg

446 ms

Fan_P_swing_small.jpg

Fan_P_swing_small.jpg

649 ms

Fan_P_Bottom_small.jpg

Fan_P_Bottom_small.jpg

439 ms

Fan_P_4_small.jpg

Fan_P_4_small.jpg

457 ms

Fan_G_FL_small.jpg

Fan_G_FL_small.jpg

463 ms

Fan_G_wall_small.jpg

Fan_G_wall_small.jpg

463 ms

Fan_G_angle_small.jpg

Fan_G_angle_small.jpg

662 ms

Fan_G_swing_small.jpg

Fan_G_swing_small.jpg

663 ms

Fan_G_Bottom_small.jpg

Fan_G_Bottom_small.jpg

670 ms

GS932HK.jpg

GS932HK.jpg

680 ms

GS941HK.jpg

GS941HK.jpg

680 ms

gp007hk.jpg

gp007hk.jpg

1297 ms

laser.jpg

laser.jpg

877 ms

res02.jpg

res02.jpg

1352 ms

main-sprite.png

main-sprite.png

99 ms

atlantic-icons.woff

atlantic-icons.woff

9 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

16 ms

atlantic-icons.woff

atlantic-icons.woff

63 ms

atlantic-icons.ttf

atlantic-icons.ttf

8 ms

atlantic-icons.ttf

atlantic-icons.ttf

269 ms

atlantic-icons.svg

atlantic-icons.svg

8 ms

atlantic-icons.svg

atlantic-icons.svg

148 ms

jquery-preload.js

jquery-preload.js

217 ms

Accessibility Review

moskiller.com accessibility score

67

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 progressbar elements do not have accessible names.

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

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

moskiller.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

moskiller.com SEO score

82

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

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Moskiller.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Moskiller.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

moskiller.com

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