1.8 sec in total
359 ms
1.3 sec
202 ms
Visit alexfuller.com now to see the best up-to-date Alexfuller content and also check out these interesting facts you probably never knew about alexfuller.com
graphic design portfolio of Alex Fuller
Visit alexfuller.comWe analyzed Alexfuller.com page load time and found that the first response time was 359 ms and then it took 1.5 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.
alexfuller.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value5.1 s
25/100
25%
Value5.1 s
62/100
10%
Value1,550 ms
13/100
30%
Value0
100/100
15%
Value8.6 s
37/100
10%
359 ms
76 ms
217 ms
387 ms
210 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 18% of them (12 requests) were addressed to the original Alexfuller.com, 72% (49 requests) were made to Payload.cargocollective.com and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (387 ms) belongs to the original domain Alexfuller.com.
Page size can be reduced by 115.2 kB (15%)
744.4 kB
629.2 kB
In fact, the total size of Alexfuller.com main page is 744.4 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. 40% of websites need less resources to load. Images take 487.3 kB which makes up the majority of the site volume.
Potential reduce by 44.6 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 44.6 kB or 86% of the original size.
Potential reduce by 6.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. Alexfuller images are well optimized though.
Potential reduce by 60.7 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 60.7 kB or 32% of the original size.
Potential reduce by 3.6 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. Alexfuller.com needs all CSS files to be minified and compressed as it can save up to 3.6 kB or 28% of the original size.
Number of requests can be reduced by 17 (25%)
67
50
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alexfuller. 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 4 to 1 for CSS and as a result speed up the page load time.
alexfuller.com
359 ms
stylesheet
76 ms
cargo.jquery.package.js
217 ms
cargo.site.package.js
387 ms
cargo.tools.package.js
210 ms
template.js
210 ms
globalstyle.css
250 ms
css
32 ms
cargo.rail.package.js
348 ms
rail.app.js
277 ms
rail.jquery.js
286 ms
rail.css
291 ms
prt_200x200_1595277574.jpg
105 ms
prt_200x200_1577984594.jpg
143 ms
prt_200x200_1569343044.jpg
138 ms
prt_200x200_1509997993.gif
144 ms
prt_200x200_1578020082.jpg
149 ms
prt_200x200_1485731766.gif
140 ms
prt_200x200_1485467739.gif
177 ms
prt_200x200_1479165211.jpg
178 ms
prt_200x200_1487715096.gif
179 ms
prt_200x200_1476388524.png
153 ms
prt_200x200_1472837064.png
180 ms
prt_200x200_1467143511.png
182 ms
prt_200x200_1462918172.gif
206 ms
prt_200x200_1478399955.jpg
203 ms
prt_200x200_1478447878.jpg
187 ms
prt_200x200_1430407318.gif
208 ms
prt_200x200_1429213257.gif
232 ms
prt_200x200_1421948774.jpg
220 ms
prt_200x200_1416949338.gif
223 ms
prt_200x200_1406838935.jpg
231 ms
prt_200x200_1404243350.gif
243 ms
prt_200x200_1404243683.jpg
240 ms
prt_200x200_1400635725.jpg
255 ms
prt_200x200_1399405787.jpg
252 ms
prt_200x200_1399406655.gif
290 ms
prt_200x200_1390762131.jpg
243 ms
prt_200x200_1374250928.jpg
273 ms
prt_200x200_1371861951.gif
277 ms
prt_200x200_1364757118.gif
281 ms
prt_200x200_1364691464.jpg
262 ms
prt_200x200_1360347732.gif
265 ms
prt_200x200_1358802857.jpg
294 ms
prt_200x200_1357269911.gif
275 ms
prt_200x200_1363617735.jpg
287 ms
prt_200x200_1347915238.gif
304 ms
prt_200x200_1383583500.gif
306 ms
loadingAnim.gif
80 ms
ga.js
49 ms
alexfuller
59 ms
analytics.js
44 ms
__utm.gif
21 ms
collect
14 ms
js
58 ms
prt_200x200_1341261415.jpg
193 ms
prt_200x200_1332365117.jpg
184 ms
prt_200x200_1314658232.jpg
164 ms
prt_200x200_1314657218.jpg
173 ms
prt_200x200_1314896540.gif
171 ms
prt_200x200_1314660326.jpg
183 ms
prt_200x200_1314716190.jpg
186 ms
prt_200x200_1314811231.gif
159 ms
prt_200x200_1314655433.jpg
176 ms
prt_200x200_1330980689.gif
168 ms
prt_200x200_1316725569.gif
155 ms
prt_200x200_1317913526.jpg
186 ms
prt_200x200_1372276126.gif
158 ms
alexfuller.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
Image elements do not have [alt] attributes
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.
alexfuller.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
alexfuller.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
![]()
EN
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alexfuller.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 Alexfuller.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.
alexfuller.com
Open Graph description is not detected on the main page of Alexfuller. 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: