Tools & Wizards About Us
issues.nerdery.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

issues.nerdery.com

Your work - Nerdery Jira Cloud

Page Load Speed

3.2 sec in total

First Response

169 ms

Resources Loaded

2.9 sec

Page Rendered

130 ms

issues.nerdery.com screenshot

About Website

Click here to check amazing Issues Nerdery content for United States. Otherwise, check out these important facts you probably never knew about issues.nerdery.com

Visit issues.nerdery.com

Key Findings

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

Performance Metrics

issues.nerdery.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value15.0 s

8/100

10%

Network Requests Diagram

issues.nerdery.com

169 ms

Dashboard.jspa

1828 ms

ruxitagentjs_2bfnqr_10080150918045144.js

165 ms

batch.css

354 ms

batch.css

402 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that all of those requests were addressed to Issues.nerdery.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Issues.nerdery.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 35.0 kB (73%)

Content Size

48.0 kB

After Optimization

12.9 kB

  • HTML
  • Images

In fact, the total size of Issues.nerdery.com main page is 48.0 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. HTML takes 47.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 35.0 kB

  • Original 47.4 kB
  • After minification 45.4 kB
  • After compression 12.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 35.0 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 2 B

  • Original 619 B
  • After minification 617 B

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. Issues Nerdery images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 17 (74%)

Requests Now

23

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

issues.nerdery.com

issues.nerdery.com

169 ms

Dashboard.jspa

Dashboard.jspa

1828 ms

ruxitagentjs_2bfnqr_10080150918045144.js

ruxitagentjs_2bfnqr_10080150918045144.js

165 ms

batch.css

batch.css

354 ms

batch.css

batch.css

402 ms

batch.css

batch.css

372 ms

batch.css

batch.css

391 ms

batch.css

batch.css

336 ms

batch.js

batch.js

1126 ms

batch.js

batch.js

961 ms

batch.js

batch.js

855 ms

batch.js

batch.js

514 ms

batch.js

batch.js

590 ms

batch.js

batch.js

628 ms

batch.js

batch.js

757 ms

batch.js

batch.js

760 ms

jira.webresources:calendar-en.js

jira.webresources:calendar-en.js

794 ms

jira.webresources:calendar-localisation-moment.js

jira.webresources:calendar-localisation-moment.js

795 ms

shortcuts.js

shortcuts.js

854 ms

com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector.js

com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector.js

398 ms

jira-logo-scaled.png

jira-logo-scaled.png

34 ms

appswitcher

appswitcher

40 ms

atlassian-icons.woff

atlassian-icons.woff

194 ms

poll

poll

97 ms

21208cf3

21208cf3

35 ms

tools_20.png

tools_20.png

40 ms

Accessibility Review

issues.nerdery.com accessibility score

98

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.

Best Practices

issues.nerdery.com best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

issues.nerdery.com SEO score

91

Search Engine Optimization Advices

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 Issues.nerdery.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 Issues.nerdery.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

issues.nerdery.com

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