Tools & Wizards About Us
moseeker.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

moseeker.com

MoSeeker仟寻招聘SaaS 一站式端到端智能化招聘解决方案

Page Load Speed

22.8 sec in total

First Response

1.2 sec

Resources Loaded

21.5 sec

Page Rendered

175 ms

moseeker.com screenshot

About Website

Visit moseeker.com now to see the best up-to-date Mo Seeker content for China and also check out these interesting facts you probably never knew about moseeker.com

MoSeeker 招聘 SaaS为企业HR团队提供招聘软件,招聘工具,渠道管理,招聘流程管理,招聘方案,校园招聘,人才招聘系统,人才管理,人才库构建和激活,数据分析,微信招聘,电话外呼,智能助理,简历解析等服务,招聘管理系统,尽在仟寻MoSeeker

Visit moseeker.com

Key Findings

We analyzed Moseeker.com page load time and found that the first response time was 1.2 sec and then it took 21.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

moseeker.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value14.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.5 s

0/100

25%

SI (Speed Index)

Value16.6 s

0/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

moseeker.com

1162 ms

app.common.ec5cd1df.css

3232 ms

app.1bcf2f02.css

4236 ms

vendor.6aae3d9f.js

19580 ms

templates.ba767249.js

19580 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 11% of them (1 request) were addressed to the original Moseeker.com, 56% (5 requests) were made to Static.moseeker.com and 22% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Static.moseeker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 248.8 kB (38%)

Content Size

649.9 kB

After Optimization

401.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Moseeker.com main page is 649.9 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. Only 10% of websites need less resources to load. Images take 375.7 kB which makes up the majority of the site volume.

HTML Optimization

-99%

Potential reduce by 203.7 kB

  • Original 205.6 kB
  • After minification 3.7 kB
  • After compression 1.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 201.8 kB, which is 98% 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 203.7 kB or 99% of the original size.

Image Optimization

-0%

Potential reduce by 1.5 kB

  • Original 375.7 kB
  • After minification 374.1 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. Mo Seeker images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

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

CSS Optimization

-74%

Potential reduce by 11.6 kB

  • Original 15.8 kB
  • After minification 15.7 kB
  • After compression 4.1 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. Moseeker.com needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 74% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mo Seeker. According to our analytics all requests are already optimized.

Network Requests Diagram

moseeker.com

moseeker.com

1162 ms

app.common.ec5cd1df.css

app.common.ec5cd1df.css

3232 ms

app.1bcf2f02.css

app.1bcf2f02.css

4236 ms

vendor.6aae3d9f.js

vendor.6aae3d9f.js

19580 ms

templates.ba767249.js

templates.ba767249.js

19580 ms

app.e7398344.js

app.e7398344.js

19580 ms

analytics.js

analytics.js

17 ms

collect

collect

33 ms

hm.js

hm.js

694 ms

Accessibility Review

moseeker.com accessibility score

69

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

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

moseeker.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

moseeker.com

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