2.9 sec in total
251 ms
2.3 sec
348 ms
Visit fflogs.com now to see the best up-to-date FF Logs content for China and also check out these interesting facts you probably never knew about fflogs.com
Welcome to FF Logs, a Web site that provides combat analysis for Square Enix's Final Fantasy XIV MMO. Record your combats, upload them to the site and analyze them
Visit fflogs.comWe analyzed Fflogs.com page load time and found that the first response time was 251 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
fflogs.com performance score
name
value
score
weighting
Value10.1 s
0/100
10%
Value10.6 s
0/100
25%
Value26.5 s
0/100
10%
Value21,300 ms
0/100
30%
Value0.19
64/100
15%
Value54.2 s
0/100
10%
251 ms
252 ms
90 ms
156 ms
157 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 21% of them (17 requests) were addressed to the original Fflogs.com, 9% (7 requests) were made to Googleads.g.doubleclick.net and 7% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (565 ms) belongs to the original domain Fflogs.com.
Page size can be reduced by 1.2 MB (63%)
1.8 MB
682.7 kB
In fact, the total size of Fflogs.com 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. 65% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 25.5 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 25.5 kB or 80% of the original size.
Potential reduce by 58.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, FF Logs needs image optimization as it can save up to 58.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.0 MB
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 1.0 MB or 73% of the original size.
Potential reduce by 49.3 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. Fflogs.com needs all CSS files to be minified and compressed as it can save up to 49.3 kB or 83% of the original size.
Number of requests can be reduced by 53 (69%)
77
24
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FF Logs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
fflogs.com
251 ms
www.fflogs.com
252 ms
jquery-ui-1.8.21.custom.css
90 ms
global.css
156 ms
global-ff.css
157 ms
fonts.css
175 ms
sm-core-css.css
186 ms
sm-black.css
187 ms
jquery.min.js
306 ms
jquery-ui.min.js
393 ms
jquery.smartmenus.js
233 ms
jquery.dataTables.js
565 ms
adsbygoogle.js
4 ms
header-logo.png
218 ms
twitter.png
83 ms
analytics.js
13 ms
ca-pub-1955439907736310.js
80 ms
zrt_lookup.html
132 ms
show_ads_impl.js
78 ms
header-bg.jpg
500 ms
Raleway-Regular-webfont.woff
154 ms
mesh.jpg
473 ms
ads
160 ms
osd.js
12 ms
ads
200 ms
ads
204 ms
129 ms
adj
75 ms
beacon
65 ms
7871101546598716575
28 ms
abg.js
29 ms
m_js_controller.js
40 ms
googlelogo_color_112x36dp.png
39 ms
120 ms
adj
62 ms
beacon
47 ms
s
37 ms
x_button_blue2.png
38 ms
smart_tag.js
365 ms
verify_selector.js
186 ms
blank.gif
195 ms
beacon.js
110 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
2 ms
verify_selector.js
255 ms
blank.gif
254 ms
30082-220467-9866-1
7 ms
30082-220467-9866-1
13 ms
IMM_StraightTalk_01142016_AWS_Display_Q1-16_Tax-Time_General_None_v1_ST00965_728x90.jpg
258 ms
inv_a.js
47 ms
dvtp_src.js
71 ms
augur.min.js
161 ms
augur.min.js
209 ms
dvtp_src_internal25.js
11 ms
t2tv7.html
179 ms
visit.js
190 ms
visit.js
133 ms
_.htm
57 ms
verifyr.js
74 ms
verifyr.js
60 ms
ad
76 ms
img.gif
40 ms
ad
65 ms
0
191 ms
avs5634.js
48 ms
query.js
101 ms
event.gif
169 ms
bg.png
67 ms
pixel
55 ms
lidar.js
26 ms
sbhK2lTE.js
25 ms
pixel
54 ms
adchoices.en.png
49 ms
event.gif
153 ms
event.gif
146 ms
event.jpg
154 ms
event.jpg
153 ms
cTrvNaRi.html
39 ms
pixel
120 ms
pixel
121 ms
query.js
57 ms
event.gif
28 ms
sd
4 ms
fflogs.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
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>).
fflogs.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fflogs.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fflogs.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 Fflogs.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.
fflogs.com
Open Graph description is not detected on the main page of FF Logs. 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: