Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

factecards.com

7阶梯式超级倍投法-大发一分稳定计划-(中国)搜狗百科-

Page Load Speed

5 sec in total

First Response

985 ms

Resources Loaded

3.3 sec

Page Rendered

656 ms

factecards.com screenshot

About Website

Click here to check amazing Factecards content for United States. Otherwise, check out these important facts you probably never knew about factecards.com

Cool, Fun, Weird Facts on E-Cards

Visit factecards.com

Key Findings

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

Performance Metrics

factecards.com performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value11.1 s

5/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

factecards.com

985 ms

jquery.min.js

37 ms

css

29 ms

style.css

224 ms

jetpack.css

184 ms

Our browser made a total of 158 requests to load all elements on the main page. We found that 40% of them (63 requests) were addressed to the original Factecards.com, 13% (20 requests) were made to Um.simpli.fi and 3% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Factecards.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 437.1 kB (22%)

Content Size

2.0 MB

After Optimization

1.6 MB

In fact, the total size of Factecards.com main page is 2.0 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. 75% 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. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 108.2 kB

  • Original 129.0 kB
  • After minification 113.8 kB
  • After compression 20.8 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 15.2 kB, which is 12% 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 108.2 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 41.9 kB

  • Original 1.4 MB
  • After minification 1.4 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. Factecards images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 162.9 kB

  • Original 290.7 kB
  • After minification 285.8 kB
  • After compression 127.8 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 162.9 kB or 56% of the original size.

CSS Optimization

-84%

Potential reduce by 124.1 kB

  • Original 148.5 kB
  • After minification 131.3 kB
  • After compression 24.4 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. Factecards.com needs all CSS files to be minified and compressed as it can save up to 124.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (51%)

Requests Now

132

After Optimization

65

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

Accessibility Review

factecards.com accessibility score

43

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

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

High

Image elements do not have [alt] attributes

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

factecards.com best practices score

67

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

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

factecards.com SEO score

64

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

High

robots.txt is not valid

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Factecards.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Factecards.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 Factecards. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: