2.3 sec in total
377 ms
1.8 sec
179 ms
Click here to check amazing Franz content for United States. Otherwise, check out these important facts you probably never knew about franz.com
Franz Inc. is an early innovator in Artificial Intelligence (AI) and leading supplier of Semantic Graph Database technology (AllegroGraph) with expert knowledge in developing and deploying Knowledge G...
Visit franz.comWe analyzed Franz.com page load time and found that the first response time was 377 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
franz.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value7.2 s
5/100
25%
Value5.2 s
59/100
10%
Value1,050 ms
25/100
30%
Value0.451
20/100
15%
Value9.9 s
27/100
10%
377 ms
54 ms
213 ms
159 ms
161 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 44% of them (29 requests) were addressed to the original Franz.com, 5% (3 requests) were made to Facebook.com and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (652 ms) relates to the external source Pixel.rubiconproject.com.
Page size can be reduced by 457.2 kB (64%)
718.6 kB
261.3 kB
In fact, the total size of Franz.com main page is 718.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. 50% of websites need less resources to load. CSS take 271.6 kB which makes up the majority of the site volume.
Potential reduce by 64.0 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 26.5 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 64.0 kB or 85% of the original size.
Potential reduce by 14.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, Franz needs image optimization as it can save up to 14.9 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 151.8 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 151.8 kB or 61% of the original size.
Potential reduce by 226.6 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. Franz.com needs all CSS files to be minified and compressed as it can save up to 226.6 kB or 83% of the original size.
Number of requests can be reduced by 43 (72%)
60
17
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Franz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
franz.com
377 ms
plusone.js
54 ms
franz.css
213 ms
swfobject.js
159 ms
site.js
161 ms
lg_franz.gif
159 ms
icn_japan_flag.png
159 ms
icn_southkorea_flag.png
207 ms
icn_france_flag.png
314 ms
icn_brazil_flag.png
314 ms
icn_china_flag.png
316 ms
icn_germany_flag.png
316 ms
icn_russia_flag.png
371 ms
icn_spain_flag.png
368 ms
cb=gapi.loaded_0
74 ms
btn_download_01.png
304 ms
in.js
24 ms
all.js
21 ms
gplus-16.png
26 ms
buzz-icon.png
235 ms
feed-icon-14x14.png
234 ms
twitter-m.png
236 ms
conversion.js
23 ms
ga.js
97 ms
secureAnonymousFramework
132 ms
bg_body_1.jpg
164 ms
bg_hdr_blue_01.png
164 ms
srchbtn_bg_01.png
164 ms
bg_nav.png
164 ms
nav_brk.png
163 ms
bg_grybttm_01.png
163 ms
bg_hmblue_01.png
244 ms
img_swtsm_01.png
243 ms
bg_hmgreen_02.png
245 ms
img_edtsm_01.png
316 ms
bg_download_02.jpg
242 ms
bg_mdl_01.png
242 ms
234 ms
130 ms
xd_arbiter.php
64 ms
xd_arbiter.php
129 ms
506e2458d2cdcc00020000c0.js
119 ms
7RZzILfRhNY
205 ms
sprite_connect_v14.png
73 ms
collect
89 ms
73 ms
tagjs
28 ms
64 ms
103 ms
adsct
129 ms
Pug
126 ms
pixel
107 ms
www-embed-player-vflZsBgOl.css
96 ms
www-embed-player.js
127 ms
base.js
201 ms
unsupportedbrowser
132 ms
cb
31 ms
sd
22 ms
cb
11 ms
unsupportedbrowser
109 ms
cb
6 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
14 ms
ad_status.js
66 ms
tap.php
652 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
103 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
110 ms
franz.com accessibility score
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
[role]s are not contained by their required parent element
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
Form elements do not have associated labels
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
franz.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
franz.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Franz.com 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 Franz.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
franz.com
Open Graph data is detected on the main page of Franz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: