Report Summary

  • 23

    Performance

    Renders faster than
    43% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

jogg.se

Jogg - Träningsdagbok & community

Page Load Speed

5.9 sec in total

First Response

1.6 sec

Resources Loaded

3.5 sec

Page Rendered

803 ms

jogg.se screenshot

About Website

Visit jogg.se now to see the best up-to-date Jogg content for Sweden and also check out these interesting facts you probably never knew about jogg.se

Sveriges största mötesplats för löpare med över 300.000 medlemmar. Här hittar du löparkompisar, löpardagbok, forum, rundor och mycket annat. Artiklar om löpning, löparapp och träningsdagbok gratis.

Visit jogg.se

Key Findings

We analyzed Jogg.se page load time and found that the first response time was 1.6 sec and then it took 4.3 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

jogg.se performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value28.4 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

jogg.se

1584 ms

normalize.css

308 ms

css

26 ms

main.css

528 ms

journal.css

320 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 64% of them (53 requests) were addressed to the original Jogg.se, 5% (4 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Jogg.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 756.5 kB (41%)

Content Size

1.8 MB

After Optimization

1.1 MB

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

HTML Optimization

-81%

Potential reduce by 122.7 kB

  • Original 151.0 kB
  • After minification 120.6 kB
  • After compression 28.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. This page needs HTML code to be minified as it can gain 30.4 kB, which is 20% 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 122.7 kB or 81% of the original size.

Image Optimization

-13%

Potential reduce by 125.4 kB

  • Original 957.2 kB
  • After minification 831.9 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, Jogg needs image optimization as it can save up to 125.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 357.3 kB

  • Original 548.2 kB
  • After minification 513.7 kB
  • After compression 191.0 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 357.3 kB or 65% of the original size.

CSS Optimization

-86%

Potential reduce by 151.2 kB

  • Original 176.3 kB
  • After minification 116.8 kB
  • After compression 25.1 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. Jogg.se needs all CSS files to be minified and compressed as it can save up to 151.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (31%)

Requests Now

74

After Optimization

51

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

Accessibility Review

jogg.se accessibility score

70

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

[role] values are not valid

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

jogg.se 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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

jogg.se SEO score

76

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

    SV

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jogg.se can be misinterpreted by Google and other search engines. Our service has detected that Swedish 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 Jogg.se 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 Jogg. 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: