2.6 sec in total
670 ms
1.6 sec
339 ms
Welcome to faithz.com homepage info - get ready to check FaithZ best content for United States right away, or after learning these important things about faithz.com
shop fr BJD Azone, Angel Philia, Pullip, Nendoroid, Figma, Chongokin, Hi-Metal, Metal Build,
Visit faithz.comWe analyzed Faithz.com page load time and found that the first response time was 670 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
faithz.com performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value7.1 s
6/100
25%
Value4.8 s
67/100
10%
Value20 ms
100/100
30%
Value0.36
30/100
15%
Value4.3 s
84/100
10%
670 ms
18 ms
115 ms
116 ms
118 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 98% of them (83 requests) were addressed to the original Faithz.com, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (806 ms) belongs to the original domain Faithz.com.
Page size can be reduced by 474.6 kB (18%)
2.6 MB
2.1 MB
In fact, the total size of Faithz.com main page is 2.6 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. 50% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 74.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 74.5 kB or 87% of the original size.
Potential reduce by 211.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. FaithZ images are well optimized though.
Potential reduce by 120.0 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 120.0 kB or 73% of the original size.
Potential reduce by 68.2 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. Faithz.com needs all CSS files to be minified and compressed as it can save up to 68.2 kB or 80% of the original size.
Number of requests can be reduced by 34 (41%)
83
49
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FaithZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
faithz.com
670 ms
css
18 ms
style_imagehover.css
115 ms
style_wishlist_classic.css
116 ms
stylesheet.css
118 ms
stylesheet_boxes.css
117 ms
stylesheet_css_buttons.css
120 ms
stylesheet_ezpages_footer_columns.css
181 ms
stylesheet_header_menu.css
178 ms
stylesheet_lightbox-0.5.css
178 ms
stylesheet_main.css
236 ms
stylesheet_reward.css
180 ms
stylesheet_social_media_icons.css
235 ms
stylesheet_tm.css
293 ms
stylesheet_topmenu.css
238 ms
index_home.css
237 ms
jscript_imagehover.js
292 ms
jscript_jquery-1.7.1.min.js
449 ms
jscript_jquery.nivo.slider.pack.js
300 ms
jscript_script.js
301 ms
jscript_utils.js
349 ms
jscript_xdropdown_menu.js
349 ms
jscript_xeasyTooltip.js
351 ms
jscript_xjquery.easing.1.3.js
354 ms
jscript_xjquery.jqtransform.js
401 ms
jscript_xjquery.lightbox-0.5.js
462 ms
jscript_zjquery.faded.js
407 ms
bg-main-2.png
114 ms
logo.jpg
235 ms
icon.gif
164 ms
icon.gif
234 ms
AP.jpg
454 ms
a2.jpg
388 ms
a6.jpg
452 ms
a1.jpg
451 ms
a3.jpg
514 ms
b1.jpg
333 ms
b10.jpg
449 ms
b9.jpg
446 ms
b13.jpg
503 ms
b8.jpg
506 ms
b7.jpg
514 ms
b6.jpg
516 ms
b5.jpg
515 ms
b4.jpg
561 ms
b3.jpg
564 ms
b2.jpg
571 ms
b11.jpg
571 ms
fbfa5e7215c1c45a4c759747b5490bb3.image.175x250.jpg
572 ms
f7ced73c1ece23607ae40b6797441dff.image.177x250.jpg
573 ms
a2960a3d88b6202f1061fe0554d9f3f1.image.176x250.jpg
618 ms
c0dfd28104caf2d00d554e0bb7af8a82.image.250x250.png
806 ms
6905869a4662172dce56ad135882a4e9.image.250x250.jpg
626 ms
a655422a8e9b14ae1c15d809114df8a0.image.166x250.jpg
627 ms
a91693bb251fc7224d62f45550e8f5e1.image.166x250.jpg
586 ms
2c35051e2fedfe57b755786c7eec301f.image.250x250.jpg
580 ms
f865e61f27f9314fb23b7cd6c65bc2c8.image.166x250.jpg
626 ms
5b6df6a5849bc41d55c67890b1bc53b9.image.208x250.jpg
633 ms
780e52403ed8319ebb4bef10ca8aa2f1.image.166x250.jpg
630 ms
66ca8247ceada9577d53990a037ab30d.image.250x250.jpg
584 ms
XieLian.jpg
581 ms
54224e4b6dc158b65dd01a68ed468329.image.166x250.jpg
623 ms
ef4b68aa5f3bbc8651c94d44cc996863.image.166x250.jpg
585 ms
95613d4ce7f8f910f02df0e6a0bbdf7d.image.166x250.jpg
584 ms
7be5ef1f464bb7a08374c9746ef43be0.image.166x250.jpg
514 ms
281d72a065a359c89a3790b54561eba9.image.166x250.jpg
516 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhDuXMQQ.woff
7 ms
59111fb22d54a760b2c76adcd2d0032e.image.166x250.jpg
558 ms
fd204afb03c6e2e642d731e814f71d6c.image.166x250.jpg
475 ms
ec1f87c7cf5f3775e197c196adf833a1.image.166x250.JPG
422 ms
b4fa1582838e82324702f961b98710d4.image.166x250.jpg
363 ms
127013cfbc42d0a4f499af3de70d970e.image.166x250.jpg
360 ms
08aba40fab49bce2f3c8e4d380cccdb1.image.166x250.jpg
401 ms
6bb677750a7a7ce94c9f505d6f86541c.image.166x250.jpg
414 ms
menu-marker.png
414 ms
facebook.png
362 ms
twitter.png
361 ms
rss.png
352 ms
search.gif
394 ms
nav_sp.png
407 ms
menu_0.png
407 ms
menu_6.gif
363 ms
cur-arrow.gif
359 ms
pagination.png
353 ms
print_stylesheet.css
59 ms
faithz.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.
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
Links do not have a discernible name
faithz.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
faithz.com SEO score
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 doesn't use 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 Faithz.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 Faithz.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.
faithz.com
Open Graph description is not detected on the main page of FaithZ. 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: