1.8 sec in total
76 ms
1 sec
658 ms
Click here to check amazing Century Seals content. Otherwise, check out these important facts you probably never knew about centuryseals.com
Visit centuryseals.comWe analyzed Centuryseals.com page load time and found that the first response time was 76 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
centuryseals.com performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value10.7 s
0/100
25%
Value6.3 s
41/100
10%
Value340 ms
74/100
30%
Value0.016
100/100
15%
Value8.9 s
35/100
10%
76 ms
148 ms
77 ms
68 ms
287 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 19% of them (29 requests) were addressed to the original Centuryseals.com, 66% (99 requests) were made to Ka-p.fontawesome.com and 8% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (397 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 27.6 kB (1%)
3.6 MB
3.6 MB
In fact, the total size of Centuryseals.com main page is 3.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. 85% 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 2.9 MB which makes up the majority of the site volume.
Potential reduce by 22.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. 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 22.0 kB or 76% of the original size.
Potential reduce by 2.1 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. Century Seals images are well optimized though.
Potential reduce by 1.4 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.
Potential reduce by 2.1 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. Centuryseals.com has all CSS files already compressed.
Number of requests can be reduced by 18 (47%)
38
20
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Century Seals. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
centuryseals.com
76 ms
www.centuryseals.com
148 ms
js
77 ms
0829c9bdb1.css
68 ms
all.js
287 ms
bootstrap.min.css
50 ms
styles.css
68 ms
design.css
69 ms
fancybox.min.css
75 ms
jquery-3.0.0.min.js
148 ms
popper.min.js
39 ms
bootstrap.min.js
137 ms
fancybox.min.js
137 ms
css2
47 ms
api.js
58 ms
cfform.js
135 ms
mask.js
135 ms
api.js
100 ms
ajax.js
134 ms
pro.min.css
135 ms
pro-v4-shims.min.css
168 ms
pro-v5-font-face.min.css
199 ms
pro-v4-font-face.min.css
181 ms
old-logo-2.png
47 ms
carbon-fibre-v2.png
152 ms
slideshow-2-resize-3.jpg
304 ms
slideshow_3.jpg
373 ms
slideshow-4-resize-3.jpg
337 ms
watermark-big.png
77 ms
relay-header-bases_1679586325874_67.jpg
170 ms
test.jpg
235 ms
single-pin-slash-feed-through-terminals.jpg
269 ms
sight-glasses.jpg
234 ms
sensors-slash-to-packages.jpg
318 ms
dual-in-line-package-(dip)-header.jpg
336 ms
solid-side-walls-and-flat-packs.jpg
353 ms
custom-packages.jpg
383 ms
parallax-2.jpg
370 ms
old-logo-2-white.png
369 ms
iso-small-2.png
368 ms
itar-rec-3.png
383 ms
recaptcha__en.js
93 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-Y3tco5q6.ttf
132 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-Y3tco5q6.ttf
132 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-Y3tco5q6.ttf
132 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-Y3tco5q6.ttf
177 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-Y3tco5q6.ttf
147 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-Y3tco5q6.ttf
147 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-Y3tco5q6.ttf
145 ms
pro-fa-solid-900-0.ttf
45 ms
pro-fa-solid-900-1.ttf
45 ms
pro-fa-solid-900-2.ttf
45 ms
pro-fa-solid-900-3.ttf
121 ms
pro-fa-solid-900-4.ttf
111 ms
pro-fa-solid-900-5.ttf
120 ms
pro-fa-solid-900-6.ttf
120 ms
pro-fa-solid-900-7.ttf
121 ms
pro-fa-solid-900-8.ttf
110 ms
pro-fa-solid-900-9.ttf
131 ms
pro-fa-solid-900-10.ttf
131 ms
pro-fa-solid-900-11.ttf
147 ms
pro-fa-solid-900-12.ttf
145 ms
pro-fa-solid-900-13.ttf
146 ms
pro-fa-solid-900-14.ttf
145 ms
pro-fa-solid-900-15.ttf
147 ms
pro-fa-solid-900-16.ttf
148 ms
pro-fa-solid-900-17.ttf
154 ms
pro-fa-solid-900-18.ttf
167 ms
pro-fa-solid-900-19.ttf
166 ms
pro-fa-solid-900-20.ttf
168 ms
pro-fa-solid-900-21.ttf
154 ms
pro-fa-solid-900-22.ttf
167 ms
pro-fa-regular-400-0.ttf
169 ms
pro-fa-regular-400-1.ttf
172 ms
pro-fa-regular-400-2.ttf
186 ms
pro-fa-regular-400-3.ttf
173 ms
pro-fa-regular-400-4.ttf
174 ms
pro-fa-regular-400-5.ttf
194 ms
pro-fa-regular-400-6.ttf
194 ms
pro-fa-regular-400-7.ttf
186 ms
pro-fa-regular-400-8.ttf
186 ms
pro-fa-regular-400-9.ttf
187 ms
pro-fa-regular-400-10.ttf
188 ms
pro-fa-regular-400-11.ttf
205 ms
pro-fa-regular-400-12.ttf
194 ms
z7NOdRfiaC4Vd8hhoPzfb5vBTP2D6quhTfmrHsLu.ttf
206 ms
z7NOdRfiaC4Vd8hhoPzfb5vBTP266quhTfmrHsLu.ttf
306 ms
z7NOdRfiaC4Vd8hhoPzfb5vBTP1v7auhTfmrHsLu.ttf
397 ms
z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7auhTfmrHsLu.ttf
311 ms
z7NOdRfiaC4Vd8hhoPzfb5vBTP0D7auhTfmrHsLu.ttf
210 ms
pro-fa-regular-400-13.ttf
174 ms
pro-fa-regular-400-14.ttf
166 ms
pro-fa-regular-400-15.ttf
169 ms
pro-fa-regular-400-16.ttf
108 ms
pro-fa-regular-400-17.ttf
102 ms
pro-fa-regular-400-18.ttf
96 ms
pro-fa-regular-400-19.ttf
110 ms
pro-fa-regular-400-20.ttf
128 ms
pro-fa-regular-400-21.ttf
109 ms
pro-fa-regular-400-22.ttf
101 ms
pro-fa-light-300-0.ttf
100 ms
pro-fa-light-300-1.ttf
85 ms
pro-fa-light-300-2.ttf
96 ms
pro-fa-light-300-3.ttf
96 ms
pro-fa-light-300-4.ttf
118 ms
pro-fa-light-300-5.ttf
118 ms
pro-fa-light-300-6.ttf
95 ms
pro-fa-light-300-7.ttf
92 ms
pro-fa-light-300-8.ttf
82 ms
pro-fa-light-300-9.ttf
110 ms
pro-fa-light-300-10.ttf
98 ms
pro-fa-light-300-11.ttf
96 ms
pro-fa-light-300-12.ttf
97 ms
pro-fa-light-300-13.ttf
95 ms
pro-fa-light-300-14.ttf
104 ms
pro-fa-light-300-15.ttf
104 ms
pro-fa-light-300-16.ttf
93 ms
pro-fa-light-300-17.ttf
103 ms
pro-fa-light-300-18.ttf
92 ms
pro-fa-light-300-19.ttf
100 ms
pro-fa-light-300-20.ttf
101 ms
pro-fa-light-300-21.ttf
97 ms
pro-fa-light-300-22.ttf
97 ms
pro-fa-thin-100-0.ttf
100 ms
pro-fa-thin-100-1.ttf
101 ms
pro-fa-thin-100-2.ttf
122 ms
pro-fa-thin-100-3.ttf
101 ms
pro-fa-thin-100-4.ttf
94 ms
pro-fa-thin-100-5.ttf
94 ms
pro-fa-thin-100-6.ttf
100 ms
pro-fa-thin-100-7.ttf
98 ms
pro-fa-thin-100-8.ttf
87 ms
pro-fa-thin-100-9.ttf
99 ms
pro-fa-thin-100-10.ttf
98 ms
pro-fa-thin-100-11.ttf
99 ms
pro-fa-thin-100-12.ttf
89 ms
pro-fa-thin-100-13.ttf
91 ms
pro-fa-thin-100-14.ttf
100 ms
pro-fa-thin-100-15.ttf
99 ms
pro-fa-thin-100-16.ttf
96 ms
pro-fa-thin-100-17.ttf
108 ms
pro-fa-thin-100-18.ttf
97 ms
pro-fa-thin-100-19.ttf
94 ms
pro-fa-thin-100-20.ttf
80 ms
pro-fa-thin-100-21.ttf
90 ms
pro-fa-thin-100-22.ttf
91 ms
pro-fa-brands-400-0.ttf
89 ms
pro-fa-brands-400-1.ttf
94 ms
pro-fa-brands-400-2.ttf
84 ms
centuryseals.com accessibility score
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.
centuryseals.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
Page has valid source maps
centuryseals.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
robots.txt is not valid
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Centuryseals.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 Centuryseals.com main page’s claimed encoding is iso-8859-1. 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.
centuryseals.com
Open Graph description is not detected on the main page of Century Seals. 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: