Tools & Wizards About Us
tombraider.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

tombraider.com

Tomb Raider

Page Load Speed

2 sec in total

First Response

374 ms

Resources Loaded

1.5 sec

Page Rendered

116 ms

tombraider.com screenshot

About Website

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

Visit tombraider.com

Key Findings

We analyzed Tombraider.com page load time and found that the first response time was 374 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

tombraider.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value21.7 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value4,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.168

70/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

Network Requests Diagram

374 ms

modernizr.js

33 ms

global.css

60 ms

wp-emoji-release.min.js

25 ms

analytics.js

21 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 88% of them (14 requests) were addressed to the original Tombraider.com, 13% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (374 ms) belongs to the original domain Tombraider.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 138.0 kB (51%)

Content Size

268.8 kB

After Optimization

130.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tombraider.com main page is 268.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. 20% of websites need less resources to load. Javascripts take 98.2 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 7.8 kB

  • Original 11.1 kB
  • After minification 10.7 kB
  • After compression 3.3 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 7.8 kB or 71% of the original size.

Image Optimization

-5%

Potential reduce by 4.4 kB

  • Original 90.5 kB
  • After minification 86.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. Tomb Raider images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 65.6 kB

  • Original 98.2 kB
  • After minification 88.9 kB
  • After compression 32.6 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 65.6 kB or 67% of the original size.

CSS Optimization

-87%

Potential reduce by 60.1 kB

  • Original 69.0 kB
  • After minification 50.9 kB
  • After compression 8.9 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. Tombraider.com needs all CSS files to be minified and compressed as it can save up to 60.1 kB or 87% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

374 ms

modernizr.js

modernizr.js

33 ms

global.css

global.css

60 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

25 ms

analytics.js

analytics.js

21 ms

landing.jpg

landing.jpg

46 ms

drop-background.jpg

drop-background.jpg

38 ms

age-us.png

age-us.png

39 ms

age-uk.png

age-uk.png

41 ms

age-de.png

age-de.png

39 ms

age-es.png

age-es.png

263 ms

age-fr.png

age-fr.png

67 ms

age-it.png

age-it.png

63 ms

lower-repeat.png

lower-repeat.png

81 ms

landing-esrb.jpg

landing-esrb.jpg

65 ms

collect

collect

11 ms

Accessibility Review

tombraider.com accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

tombraider.com best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tombraider.com SEO score

82

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tombraider.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Tombraider.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

tombraider.com

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