Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

runmygeek.com

奔腾 - 818App资源库

Page Load Speed

4.1 sec in total

First Response

73 ms

Resources Loaded

3.3 sec

Page Rendered

719 ms

runmygeek.com screenshot

About Website

Visit runmygeek.com now to see the best up-to-date Runmygeek content and also check out these interesting facts you probably never knew about runmygeek.com

手机应用市场有哪些?✅安卓应用市场哪个好?✅App下载资源网✅整理了最好用的应用市场下载手机版,包括华为应用市场、360应用市场、应用宝、木蚂蚁应用市场等,还有手机应用市场排行榜供大家参考选择哦!需要安卓第三方应用市场的朋友,赶快来看一看吧!

Visit runmygeek.com

Key Findings

We analyzed Runmygeek.com page load time and found that the first response time was 73 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

runmygeek.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

runmygeek.com

73 ms

www.runmygeek.com

792 ms

3645911276-widget_css_bundle.css

46 ms

authorization.css

245 ms

plusone.js

56 ms

Our browser made a total of 216 requests to load all elements on the main page. We found that 1% of them (3 requests) were addressed to the original Runmygeek.com, 15% (33 requests) were made to Apis.google.com and 9% (20 requests) were made to Blog.runmygeek.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Snapwidget.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.6 MB (30%)

Content Size

15.6 MB

After Optimization

11.0 MB

In fact, the total size of Runmygeek.com main page is 15.6 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. Only a small number of websites need less resources to load. Images take 14.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 218.5 kB

  • Original 274.3 kB
  • After minification 273.7 kB
  • After compression 55.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 218.5 kB or 80% of the original size.

Image Optimization

-25%

Potential reduce by 3.5 MB

  • Original 14.0 MB
  • After minification 10.5 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, Runmygeek needs image optimization as it can save up to 3.5 MB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 801.3 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 389.3 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 801.3 kB or 67% of the original size.

CSS Optimization

-74%

Potential reduce by 110.1 kB

  • Original 147.9 kB
  • After minification 147.4 kB
  • After compression 37.8 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. Runmygeek.com needs all CSS files to be minified and compressed as it can save up to 110.1 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 90 (42%)

Requests Now

212

After Optimization

122

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

Accessibility Review

runmygeek.com accessibility score

54

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

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

SEO Factors

runmygeek.com SEO score

84

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

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