Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 67

    SEO

    Google-friendlier than
    35% of websites

forgeworld.co.uk

Queue-it

Page Load Speed

38.1 sec in total

First Response

953 ms

Resources Loaded

30.9 sec

Page Rendered

6.3 sec

forgeworld.co.uk screenshot

About Website

Welcome to forgeworld.co.uk homepage info - get ready to check Forgeworld best content for United States right away, or after learning these important things about forgeworld.co.uk

Visit forgeworld.co.uk

Key Findings

We analyzed Forgeworld.co.uk page load time and found that the first response time was 953 ms and then it took 37.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 27 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

forgeworld.co.uk performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value21.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value30.1 s

0/100

25%

SI (Speed Index)

Value21.6 s

0/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value28.2 s

0/100

10%

Network Requests Diagram

www.forgeworld.co.uk

953 ms

FW-Home

974 ms

combined.css.h1291871396.pack

430 ms

combined.css.h-1904432605.pack

691 ms

combined.css.h-1018361893.pack

1828 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 81% of them (68 requests) were addressed to the original Forgeworld.co.uk, 14% (12 requests) were made to Cdnazure-socialannexinc.netdna-ssl.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (21.8 sec) belongs to the original domain Forgeworld.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 454.1 kB (8%)

Content Size

5.9 MB

After Optimization

5.5 MB

In fact, the total size of Forgeworld.co.uk main page is 5.9 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 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 53.7 kB

  • Original 67.0 kB
  • After minification 67.0 kB
  • After compression 13.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 53.7 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 44.3 kB

  • Original 5.4 MB
  • After minification 5.3 MB

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

JavaScript Optimization

-74%

Potential reduce by 356.2 kB

  • Original 482.6 kB
  • After minification 416.6 kB
  • After compression 126.4 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 356.2 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (47%)

Requests Now

38

After Optimization

20

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

Accessibility Review

forgeworld.co.uk accessibility score

89

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

forgeworld.co.uk 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

forgeworld.co.uk SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 uses legible font sizes

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 Forgeworld.co.uk 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 Forgeworld.co.uk 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 Forgeworld. 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: