Tools & Wizards About Us
gcore.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

gcore.com

Gcore | Global Hosting, CDN, Edge and Cloud Services

Page Load Speed

3.3 sec in total

First Response

13 ms

Resources Loaded

2 sec

Page Rendered

1.3 sec

gcore.com screenshot

About Website

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

We provide powerful solutions that will help your business grow globally. Try our superior performance for free

Visit gcore.com

Key Findings

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

Performance Metrics

gcore.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

1/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value10,670 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

gcore.com

13 ms

gcore.com

684 ms

monserrat.css

115 ms

styles.cec94d3175ec34ad.css

405 ms

config.js

97 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 81% of them (22 requests) were addressed to the original Gcore.com, 19% (5 requests) were made to Assets.gcore.pro. The less responsive or slowest element that took the longest time to load (870 ms) relates to the external source Assets.gcore.pro.

Page Optimization Overview & Recommendations

Page size can be reduced by 422.0 kB (45%)

Content Size

946.8 kB

After Optimization

524.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 285.5 kB

  • Original 346.1 kB
  • After minification 343.6 kB
  • After compression 60.6 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 285.5 kB or 83% of the original size.

Image Optimization

-28%

Potential reduce by 104.7 kB

  • Original 374.5 kB
  • After minification 269.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. Obviously, Gcore needs image optimization as it can save up to 104.7 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 27.8 kB

  • Original 205.6 kB
  • After minification 205.6 kB
  • After compression 177.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 27.8 kB or 14% of the original size.

CSS Optimization

-19%

Potential reduce by 4.0 kB

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

Requests Breakdown

Number of requests can be reduced by 3 (12%)

Requests Now

25

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gcore.com

gcore.com

13 ms

gcore.com

gcore.com

684 ms

monserrat.css

monserrat.css

115 ms

styles.cec94d3175ec34ad.css

styles.cec94d3175ec34ad.css

405 ms

config.js

config.js

97 ms

runtime.55cf6dda9105298b.js

runtime.55cf6dda9105298b.js

117 ms

polyfills.84e9f98d4302be90.js

polyfills.84e9f98d4302be90.js

466 ms

main.6acf079f5cbca5a1.js

main.6acf079f5cbca5a1.js

803 ms

nvidia-partner.svg

nvidia-partner.svg

118 ms

dell-partner.svg

dell-partner.svg

114 ms

intel-partner.svg

intel-partner.svg

144 ms

ai-infrastructure.png

ai-infrastructure.png

870 ms

cloud-control-1.webp

cloud-control-1.webp

128 ms

wargaming.svg

wargaming.svg

120 ms

xsolla.svg

xsolla.svg

124 ms

jsdelivr.svg

jsdelivr.svg

122 ms

orange.svg

orange.svg

126 ms

avast.svg

avast.svg

235 ms

illustration.502a1d03fc3eefdd.png

illustration.502a1d03fc3eefdd.png

241 ms

made-lux.svg

made-lux.svg

238 ms

eco.svg

eco.svg

242 ms

guinness.svg

guinness.svg

316 ms

mastercard.svg

mastercard.svg

274 ms

paypal.svg

paypal.svg

313 ms

viza.svg

viza.svg

309 ms

mastercard_v.svg

mastercard_v.svg

320 ms

visa_v.svg

visa_v.svg

376 ms

Accessibility Review

gcore.com accessibility score

92

Accessibility Issues

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

Buttons do not have an accessible name

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.

Best Practices

gcore.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

gcore.com SEO score

86

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

gcore.com

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