Tools & Wizards About Us
ofpay.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ofpay.com

江苏小旗欧飞科技有限公司,致力打造数字权益营销生态圈

Page Load Speed

30.6 sec in total

First Response

1.6 sec

Resources Loaded

28.7 sec

Page Rendered

298 ms

ofpay.com screenshot

About Website

Click here to check amazing Ofpay content for China. Otherwise, check out these important facts you probably never knew about ofpay.com

致力打造数字权益营销生态圈，为全行业客户提供“数字权益分发+精准客户营销+SaaS服务及定制开发服务+综合运营服务”的一站式数字营销解决方案，赋能合作伙伴，加速数字化转型，实现品牌驱动用户运营新增长。

Visit ofpay.com

Key Findings

We analyzed Ofpay.com page load time and found that the first response time was 1.6 sec and then it took 29 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

ofpay.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.3 s

0/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value21.2 s

1/100

10%

Network Requests Diagram

ofpay.com

1598 ms

www.ofpay.com

1972 ms

style.css

1835 ms

jquery-1.7.min.js

2467 ms

iview.min.js

2611 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 13% of them (2 requests) were addressed to the original Ofpay.com, 73% (11 requests) were made to Pic.ofcard.com and 13% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Pic.ofcard.com.

Page Optimization Overview & Recommendations

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

Content Size

620.3 kB

After Optimization

427.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ofpay.com main page is 620.3 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 347.7 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 9.1 kB

  • Original 13.6 kB
  • After minification 12.1 kB
  • After compression 4.5 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 1.5 kB, which is 11% 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 9.1 kB or 67% of the original size.

Image Optimization

-1%

Potential reduce by 2.9 kB

  • Original 347.7 kB
  • After minification 344.8 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. Ofpay images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 163.1 kB

  • Original 236.4 kB
  • After minification 224.0 kB
  • After compression 73.4 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 163.1 kB or 69% of the original size.

CSS Optimization

-79%

Potential reduce by 17.9 kB

  • Original 22.6 kB
  • After minification 20.6 kB
  • After compression 4.7 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. Ofpay.com needs all CSS files to be minified and compressed as it can save up to 17.9 kB or 79% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ofpay.com

ofpay.com

1598 ms

www.ofpay.com

www.ofpay.com

1972 ms

style.css

style.css

1835 ms

jquery-1.7.min.js

jquery-1.7.min.js

2467 ms

iview.min.js

iview.min.js

2611 ms

logo-ofpay.png

logo-ofpay.png

2114 ms

bar.png

bar.png

2541 ms

service.jpg

service.jpg

20316 ms

partner.png

partner.png

4958 ms

h.js

h.js

2364 ms

banner1.jpg

banner1.jpg

20123 ms

banner01.jpg

banner01.jpg

20123 ms

banner02.jpg

banner02.jpg

20122 ms

banner03.jpg

banner03.jpg

20123 ms

hm.gif

hm.gif

460 ms

Accessibility Review

ofpay.com accessibility score

76

Accessibility Issues

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

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

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

ofpay.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ofpay.com SEO score

92

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

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

ofpay.com

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