1.4 sec in total
281 ms
1.1 sec
111 ms
Welcome to prefixsuffix.com homepage info - get ready to check Prefix Suffix best content for United States right away, or after learning these important things about prefixsuffix.com
PrefixSuffix.com - English Word Roots Reference || Prefix, Suffix, Prefixes, Suffixes, root words, word roots, language games
Visit prefixsuffix.comWe analyzed Prefixsuffix.com page load time and found that the first response time was 281 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
prefixsuffix.com performance score
name
value
score
weighting
Value1.6 s
93/100
10%
Value2.9 s
82/100
25%
Value7.0 s
33/100
10%
Value17,170 ms
0/100
30%
Value0.001
100/100
15%
Value24.7 s
0/100
10%
281 ms
240 ms
161 ms
163 ms
164 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 56% of them (29 requests) were addressed to the original Prefixsuffix.com, 10% (5 requests) were made to Pagead2.googlesyndication.com and 10% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (590 ms) belongs to the original domain Prefixsuffix.com.
Page size can be reduced by 67.7 kB (30%)
224.2 kB
156.5 kB
In fact, the total size of Prefixsuffix.com main page is 224.2 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. 25% of websites need less resources to load. Images take 124.0 kB which makes up the majority of the site volume.
Potential reduce by 17.9 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 17.9 kB or 77% of the original size.
Potential reduce by 4.3 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. Prefix Suffix images are well optimized though.
Potential reduce by 27.2 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 27.2 kB or 50% of the original size.
Potential reduce by 18.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. Prefixsuffix.com needs all CSS files to be minified and compressed as it can save up to 18.3 kB or 80% of the original size.
Number of requests can be reduced by 33 (67%)
49
16
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prefix Suffix. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
prefixsuffix.com
281 ms
ps.css
240 ms
psacp.css
161 ms
pslnav.css
163 ms
pslnav.js
164 ms
show_ads.js
8 ms
diggthis.js
178 ms
urchin.js
19 ms
ca-pub-8013516118159005.js
65 ms
zrt_lookup.html
73 ms
show_ads_impl.js
73 ms
x-click-but21.gif
61 ms
bg01.gif
116 ms
bg_header_01.gif
114 ms
newlogo.gif
115 ms
search.jpg
114 ms
links_facebook.gif
114 ms
links_delicious.gif
181 ms
links_digg.gif
185 ms
links_furl.gif
186 ms
links_reddit.gif
182 ms
links_technorati.gif
183 ms
links_newsvine.gif
187 ms
links_live.gif
261 ms
links_yahoo.gif
262 ms
links_stumbleupon.gif
262 ms
links_blinklists.gif
263 ms
links_spurl.gif
265 ms
links_google.gif
266 ms
links_ask.gif
338 ms
links_netscape.gif
339 ms
links_squidoo.gif
339 ms
app_tp.png
590 ms
pixel.gif
59 ms
nav_closed.gif
313 ms
nav_open.gif
316 ms
bg_footer.gif
430 ms
__utm.gif
16 ms
ads
213 ms
osd.js
10 ms
ads
233 ms
ads
239 ms
css
57 ms
m_js_controller.js
29 ms
abg.js
32 ms
favicon
68 ms
nessie_icon_tiamat_white.png
35 ms
s
27 ms
googlelogo_color_112x36dp.png
52 ms
favicon
102 ms
x_button_blue2.png
3 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
5 ms
prefixsuffix.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
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
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
prefixsuffix.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
prefixsuffix.com SEO score
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prefixsuffix.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Prefixsuffix.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.
prefixsuffix.com
Open Graph description is not detected on the main page of Prefix Suffix. 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: