Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

fmg.ac

Home - Foundation for Medieval Genealogy

Page Load Speed

9.4 sec in total

First Response

4.2 sec

Resources Loaded

5.1 sec

Page Rendered

106 ms

fmg.ac screenshot

About Website

Welcome to fmg.ac homepage info - get ready to check Fmg best content for Russia right away, or after learning these important things about fmg.ac

Promoting the study of medieval genealogy and prosopography.

Visit fmg.ac

Key Findings

We analyzed Fmg.ac page load time and found that the first response time was 4.2 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

fmg.ac performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.137

79/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

fmg.ac

4204 ms

template.css

561 ms

finder.css

189 ms

jquery.min.js

474 ms

jquery-noconflict.js

191 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 80% of them (12 requests) were addressed to the original Fmg.ac, 13% (2 requests) were made to Fonts.googleapis.com and 7% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Fmg.ac.

Page Optimization Overview & Recommendations

Page size can be reduced by 222.4 kB (75%)

Content Size

297.6 kB

After Optimization

75.2 kB

In fact, the total size of Fmg.ac main page is 297.6 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. Only 10% of websites need less resources to load. Javascripts take 153.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 11.6 kB

  • Original 16.3 kB
  • After minification 15.7 kB
  • After compression 4.7 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 11.6 kB or 71% of the original size.

JavaScript Optimization

-67%

Potential reduce by 103.3 kB

  • Original 153.4 kB
  • After minification 149.1 kB
  • After compression 50.1 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 103.3 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 107.5 kB

  • Original 128.0 kB
  • After minification 111.3 kB
  • After compression 20.5 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. Fmg.ac needs all CSS files to be minified and compressed as it can save up to 107.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (69%)

Requests Now

13

After Optimization

4

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

Accessibility Review

fmg.ac 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

fmg.ac 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fmg.ac SEO score

91

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

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 Fmg.ac 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 Fmg.ac 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 Fmg. 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: