Access frakturschrift.com. Gothic & Fraktur OCR: Old European fonts Recognition

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

frakturschrift.com

193 ms

465 ms

313 ms

OneSignalSDK.js

43 ms

one-signal-init.min.js

106 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Frakturschrift.com, 86% (24 requests) were made to Pdf.abbyy.com and 4% (1 request) were made to Cdn.onesignal.com. The less responsive or slowest element that took the longest time to load (963 ms) relates to the external source Pdf.abbyy.com.

Content Size

684.8 kB

After Optimization

619.0 kB

In fact, the total size of Frakturschrift.com main page is 684.8 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. 45% of websites need less resources to load. Images take 399.8 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 58.3 kB

Original 66.8 kB
After minification 43.8 kB
After compression 8.6 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 23.1 kB, which is 35% 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 58.3 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 7.5 kB

Original 399.8 kB
After minification 392.4 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. Fraktur Schrift images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 47 B

Original 151.1 kB
After minification 151.1 kB
After compression 151.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

Original 67.0 kB
After minification 67.0 kB
After compression 67.0 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. Frakturschrift.com has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

ARIA IDs are not unique

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

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

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.

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

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

Open Graph data is detected on the main page of Fraktur Schrift. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: