8 sec in total
1.5 sec
5.7 sec
867 ms
Visit century.com now to see the best up-to-date Century content for United States and also check out these interesting facts you probably never knew about century.com
Visit century.comWe analyzed Century.com page load time and found that the first response time was 1.5 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
century.com performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value12.8 s
0/100
25%
Value18.1 s
0/100
10%
Value640 ms
46/100
30%
Value0.117
85/100
15%
Value12.6 s
14/100
10%
1474 ms
284 ms
463 ms
58 ms
75 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 76% of them (95 requests) were addressed to the original Century.com, 17% (21 requests) were made to Fonts.gstatic.com and 5% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Century.com.
Page size can be reduced by 3.7 MB (43%)
8.6 MB
4.9 MB
In fact, the total size of Century.com main page is 8.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 112.4 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 112.4 kB or 86% of the original size.
Potential reduce by 783.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. Obviously, Century needs image optimization as it can save up to 783.4 kB or 15% 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 1.8 MB
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. Century.com needs all CSS files to be minified and compressed as it can save up to 1.8 MB or 90% of the original size.
Number of requests can be reduced by 45 (45%)
101
56
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Century. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
1474 ms
wp-emoji-release.min.js
284 ms
settings.css
463 ms
css
58 ms
css
75 ms
font-awesome.css
9 ms
custom.css
373 ms
style.css
370 ms
menu.css
189 ms
js_composer_front_custom.css
1229 ms
font-awesome.min.css
468 ms
style.css
467 ms
Defaults.css
559 ms
ultimate.min.css
1299 ms
icons.css
555 ms
vidcons.css
562 ms
css
83 ms
jquery.js
665 ms
jquery-migrate.min.js
652 ms
jquery.themepunch.tools.min.js
761 ms
jquery.themepunch.revolution.min.js
670 ms
slp_widgets.js
747 ms
preloader.js
758 ms
modernizr-custom.min.js
768 ms
jquery-ui.min.js
1037 ms
js
58 ms
ultimate.min.js
967 ms
modal-all.min.js
954 ms
jparallax.min.js
863 ms
vhparallax.min.js
958 ms
mb-YTPlayer.min.js
1054 ms
cookieconsent.min.js
1001 ms
css
17 ms
css
23 ms
ts-visual-composer-extend-animations.min.css
1273 ms
ts-visual-composer-extend-front.min.css
1539 ms
css
15 ms
front_style.css
1003 ms
jquery.malihu.PageScroll2id.js
1009 ms
jquery.malihu.PageScroll2id-init.js
1114 ms
menu.js
1269 ms
social.js
1270 ms
masonry.min.js
1272 ms
wp-embed.min.js
1272 ms
js_composer_front.min.js
1301 ms
waypoints.min.js
1221 ms
ts-visual-composer-extend-backgrounds.min.js
1133 ms
ts-visual-composer-extend-front.min.js
1186 ms
logo_century.svg
195 ms
loupe.svg
231 ms
leelaBlossom_1200.jpg
264 ms
mogule_start.jpg
1020 ms
tourbillion_start.jpg
1299 ms
dragon_stone_start.jpg
1103 ms
elegance_start.jpg
1475 ms
Couture_start.jpg
933 ms
wings_of_time_start.jpg
1291 ms
icon_1.jpg
1106 ms
icon_2.jpg
1114 ms
icon_3.jpg
1201 ms
icon_4.jpg
1297 ms
Affinity_632.7.S.12.16.SK_1-300x469.jpg
1220 ms
Couture_832.7.S.203.12.SML_1-300x469.jpg
1307 ms
Prime_Time_606.7.S.A2.13.15D.QXN_1-300x469.jpg
1328 ms
Elegance_648.7.Q.N1B.12.SF_1-300x469.jpg
1416 ms
Allegria_649.1.S.12P.36.AMG_1-300x469.jpg
1476 ms
Caprice_828.7.F.12P.66.WMK_1-300x469.jpg
1481 ms
Prima_Donna_352.7.F.12P.66.WMK_1-300x469.jpg
1432 ms
Leela_Blossom_659.10.F.12P.66.RV1_1-300x469.jpg
1440 ms
Bolero_966.7.F.M2B.66.CXK_1-300x469.jpg
1519 ms
Mogul_636.2.F.12P.78.CIK_1-300x469.jpg
1542 ms
Crescendo_664.7.X.G10.69.CZK_1-300x469.jpg
1551 ms
Allegory_696.7.X.E1.50.RB2_1-300x469.jpg
1658 ms
Wings_of_Time_P.359.7.W.10i.size_.7.ZW17_1-300x469.jpg
1598 ms
Prime_Time_606.7.N.50i.13.15D.QYO_1-300x469.jpg
1669 ms
Elegance_Tourbillon_648.7.T.S1.90.CYM_1-300x469.jpg
1627 ms
Elegance_648.7.E.50i.12.15D.CYM_1-300x469.jpg
1648 ms
Elegance_Chronograph_GMT_648.7.D.50i.12.15D.CYM_1-300x469.jpg
1737 ms
pair-PrimeTime-425x469.jpg
1696 ms
pair-Elegance-425x469.jpg
1728 ms
pair-DragonStone-425x469.jpg
1751 ms
homepage_about-century_image-1.jpg
2023 ms
DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf
233 ms
DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf
49 ms
IgZJs4-7SA1XX_edsoXWog.ttf
233 ms
MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf
233 ms
EInbV5DfGHOiMmvb1Xr-hi3USBnSvpkopQaUR-2r7iU.ttf
233 ms
toadOcfmlt9b38dHJxOBGFP7R5lD_au4SZC6Ks_vyWs.ttf
193 ms
toadOcfmlt9b38dHJxOBGFP7R5lD_au4SZC6Ks_vyWs.ttf
110 ms
toadOcfmlt9b38dHJxOBGKXvKVW_haheDNrHjziJZVk.ttf
194 ms
toadOcfmlt9b38dHJxOBGKXvKVW_haheDNrHjziJZVk.ttf
163 ms
ODelI1aHBYDBqgeIAH2zlNRl0pGnog23EMYRrBmUzJQ.ttf
192 ms
toadOcfmlt9b38dHJxOBGOiMeWyi5E_-XkTgB5psiDg.ttf
194 ms
homepage_about-century_image-2.jpg
1990 ms
fontawesome-webfont.woff
100 ms
fontawesome-webfont.woff
1663 ms
about-century_image-3.jpg
1726 ms
homepage_about-century_image-3.jpg
1727 ms
homepage_about-century_image-4.jpg
1704 ms
revolution.extension.video.min.js
1057 ms
revolution.extension.slideanims.min.js
1029 ms
revolution.extension.actions.min.js
948 ms
revolution.extension.layeranimation.min.js
956 ms
revolution.extension.navigation.min.js
965 ms
ult-silk.woff
994 ms
ult-silk.woff
965 ms
ajax-loader.gif
902 ms
1200x167_bandeaux_Ladies_Fixe.jpg
900 ms
1200x167_bandeaux_Gents_Fixe.jpg
948 ms
1200x167_bandeaux_PairWatch_Fixe.jpg
981 ms
1200x167_bandeaux_AboutCentury_Fixe.jpg
1011 ms
beyond_textV3.jpg
871 ms
coloredbg.png
107 ms
revicons.woff
117 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
10 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
11 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
44 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
44 ms
PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf
44 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
46 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
47 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
46 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
44 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
44 ms
century-top.css
110 ms
century.com accessibility score
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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
century.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
century.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Century.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 Century.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.
century.com
Open Graph description is not detected on the main page of Century. 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: