Tools & Wizards About Us
gobattlelog.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

gobattlelog.com

GO Battle Log | Your Pokemon GO PvP Companion - Analyze the Meta, Log Your Battles, Auto-Generate Teams... and More!

Page Load Speed

1.1 sec in total

First Response

101 ms

Resources Loaded

790 ms

Page Rendered

188 ms

gobattlelog.com screenshot

About Website

Welcome to gobattlelog.com homepage info - get ready to check GO Battle Log best content right away, or after learning these important things about gobattlelog.com

The world’s largest crowd-sourced Pokemon GO PvP battle database. Analyze the meta, log your battles, auto-generate teams... and more!

Visit gobattlelog.com

Key Findings

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

Performance Metrics

gobattlelog.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.5 s

0/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value10,100 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.106

88/100

15%

TTI (Time to Interactive)

Value35.4 s

0/100

10%

Network Requests Diagram

gobattlelog.com

101 ms

bootstrap.min.css

83 ms

jquery-3.5.1.min.js

66 ms

popper.min.js

66 ms

bootstrap.min.js

108 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 50% of them (33 requests) were addressed to the original Gobattlelog.com, 15% (10 requests) were made to Cdn.jsdelivr.net and 6% (4 requests) were made to Stackpath.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (498 ms) relates to the external source Cdnjs.cloudflare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.4 kB (15%)

Content Size

965.1 kB

After Optimization

818.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 21.6 kB

  • Original 29.4 kB
  • After minification 25.8 kB
  • After compression 7.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 3.6 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 21.6 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 18.4 kB

  • Original 570.6 kB
  • After minification 552.3 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. GO Battle Log images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 104.5 kB

  • Original 352.2 kB
  • After minification 352.2 kB
  • After compression 247.7 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 104.5 kB or 30% of the original size.

CSS Optimization

-15%

Potential reduce by 1.9 kB

  • Original 12.9 kB
  • After minification 12.9 kB
  • After compression 11.0 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. Gobattlelog.com needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (88%)

Requests Now

60

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gobattlelog.com

gobattlelog.com

101 ms

bootstrap.min.css

bootstrap.min.css

83 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

66 ms

popper.min.js

popper.min.js

66 ms

bootstrap.min.js

bootstrap.min.js

108 ms

shepherd.min.js

shepherd.min.js

65 ms

shepherd.css

shepherd.css

119 ms

firebase-app.js

firebase-app.js

66 ms

firebase-auth.js

firebase-auth.js

102 ms

firebase-analytics.js

firebase-analytics.js

107 ms

firebaseui.js

firebaseui.js

133 ms

firebaseui.css

firebaseui.css

114 ms

firebase-auth.js

firebase-auth.js

113 ms

font-awesome.min.css

font-awesome.min.css

116 ms

typed.js@2.0.11

typed.js@2.0.11

70 ms

base.css

base.css

114 ms

js

js

114 ms

lm.js

lm.js

111 ms

index.css

index.css

156 ms

plotly.min.js

plotly.min.js

385 ms

handlebars.min.js

handlebars.min.js

456 ms

FuzzySearch.min.js

FuzzySearch.min.js

157 ms

textarea-autosize.min.js

textarea-autosize.min.js

115 ms

jquery-ui.min.js

jquery-ui.min.js

100 ms

jquery-ui.css

jquery-ui.css

65 ms

d3.v6.min.js

d3.v6.min.js

100 ms

d3-force-reuse.min.js

d3-force-reuse.min.js

156 ms

moment.min.js

moment.min.js

73 ms

daterangepicker.min.js

daterangepicker.min.js

73 ms

daterangepicker.css

daterangepicker.css

67 ms

bootstrap4-toggle.min.css

bootstrap4-toggle.min.css

73 ms

bootstrap4-toggle.min.js

bootstrap4-toggle.min.js

99 ms

GameMaster.js

GameMaster.js

160 ms

TeamRanker.js

TeamRanker.js

155 ms

Battle.js

Battle.js

155 ms

Pokemon.js

Pokemon.js

169 ms

TimelineAction.js

TimelineAction.js

159 ms

TimelineEvent.js

TimelineEvent.js

178 ms

gbl-index-eng.js

gbl-index-eng.js

214 ms

gbl-index-jpn.js

gbl-index-jpn.js

215 ms

eng-romaji.js

eng-romaji.js

254 ms

alertify.min.js

alertify.min.js

97 ms

alertify.min.css

alertify.min.css

98 ms

bootstrap.min.css

bootstrap.min.css

100 ms

jquery.cookie.min.js

jquery.cookie.min.js

498 ms

search-history.js

search-history.js

213 ms

search-history.css

search-history.css

214 ms

lz-string.min.js

lz-string.min.js

252 ms

common.js

common.js

252 ms

antimeta.js

antimeta.js

267 ms

speech.js

speech.js

252 ms

battlemode.js

battlemode.js

253 ms

teamstats.js

teamstats.js

268 ms

translate.js

translate.js

266 ms

mmrtimeline.js

mmrtimeline.js

274 ms

index.js

index.js

316 ms

css

css

30 ms

evening-lake-sky.jpg

evening-lake-sky.jpg

66 ms

aalogo.png

aalogo.png

42 ms

landing-edit.png

landing-edit.png

58 ms

landing-reports.png

landing-reports.png

36 ms

landing-amg.png

landing-amg.png

52 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

21 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

26 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

30 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

14 ms

Accessibility Review

gobattlelog.com accessibility score

87

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

button, link, and menuitem elements do not have accessible names.

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

gobattlelog.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

gobattlelog.com SEO score

75

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

High

robots.txt is not valid

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gobattlelog.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 Gobattlelog.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

gobattlelog.com

Open Graph data is detected on the main page of GO Battle Log. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: