Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

diggfun.co

DiggFun | All Games Quizzes, Trivia, Photos and Articles

Page Load Speed

4.2 sec in total

First Response

134 ms

Resources Loaded

2.3 sec

Page Rendered

1.8 sec

diggfun.co screenshot

About Website

Visit diggfun.co now to see the best up-to-date Digg Fun content for United Kingdom and also check out these interesting facts you probably never knew about diggfun.co

DiggFun has quizzes, trivia, articles, hot topics and all the trending games buzz you'll want to share with friends.

Visit diggfun.co

Key Findings

We analyzed Diggfun.co page load time and found that the first response time was 134 ms and then it took 4.1 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

diggfun.co performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

68/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value1,990 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.261

47/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

diggfun.co

134 ms

js

68 ms

swiper.min.css

66 ms

common.css

104 ms

font-awesome.min.css

219 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 21% of them (19 requests) were addressed to the original Diggfun.co, 30% (28 requests) were made to D2onsou1d2dbvi.cloudfront.net and 10% (9 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source D2onsou1d2dbvi.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 211.9 kB (12%)

Content Size

1.8 MB

After Optimization

1.5 MB

In fact, the total size of Diggfun.co 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 87.6 kB

  • Original 107.5 kB
  • After minification 107.4 kB
  • After compression 19.9 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 87.6 kB or 81% of the original size.

Image Optimization

-12%

Potential reduce by 120.5 kB

  • Original 1.0 MB
  • After minification 907.5 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, Digg Fun needs image optimization as it can save up to 120.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 2.4 kB

  • Original 604.0 kB
  • After minification 603.9 kB
  • After compression 601.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 1.4 kB

  • Original 20.6 kB
  • After minification 20.6 kB
  • After compression 19.2 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. Diggfun.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 39 (46%)

Requests Now

85

After Optimization

46

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

Accessibility Review

diggfun.co accessibility score

61

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

diggfun.co 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

diggfun.co SEO score

85

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

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

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 Diggfun.co 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 Diggfun.co 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 Digg Fun. 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: