11.7 sec in total
4.1 sec
6.1 sec
1.6 sec
Visit makingthemark.com now to see the best up-to-date Making The Mark content and also check out these interesting facts you probably never knew about makingthemark.com
Making the Mark Inc offers custom imprinted promotional products including meeting supplies, lanyards, badge holders, hats, travel accessories, custom Post it notes, bags, drink ware, healthcare produ...
Visit makingthemark.comWe analyzed Makingthemark.com page load time and found that the first response time was 4.1 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
makingthemark.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value17.1 s
0/100
25%
Value9.9 s
10/100
10%
Value7,170 ms
0/100
30%
Value0.003
100/100
15%
Value17.9 s
4/100
10%
4108 ms
105 ms
140 ms
171 ms
167 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 88% of them (90 requests) were addressed to the original Makingthemark.com, 4% (4 requests) were made to Cdn.iubenda.com and 3% (3 requests) were made to S.adroll.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Makingthemark.com.
Page size can be reduced by 376.9 kB (12%)
3.2 MB
2.9 MB
In fact, the total size of Makingthemark.com main page is 3.2 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. 65% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 76.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 76.6 kB or 83% of the original size.
Potential reduce by 217.0 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. Making The Mark images are well optimized though.
Potential reduce by 14.9 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 68.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. Makingthemark.com needs all CSS files to be minified and compressed as it can save up to 68.3 kB or 53% of the original size.
Number of requests can be reduced by 33 (34%)
96
63
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Making The Mark. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.makingthemark.com
4108 ms
bootstrap.min.css
105 ms
flexslider.css
140 ms
font-awesome.min.css
171 ms
slick.css
167 ms
lightbox.css
170 ms
vex.css
173 ms
vex-theme-default.css
170 ms
StyleSheet
261 ms
Utils.js
200 ms
jquery.min.js
231 ms
migrate-3.1.0.js
201 ms
bootstrap.min.js
200 ms
slick.min.js
201 ms
hoverIntent.min.js
233 ms
superfish.min.js
233 ms
jquery.validate.min.js
233 ms
jquery.flexslider-min.js
234 ms
lightbox.js
265 ms
ie10-viewport-bug-workaround.js
266 ms
iframeResizer.min.js
268 ms
IFrameUtils.js
267 ms
vex.combined.js
269 ms
custom.js
367 ms
Pic
371 ms
highslide-full.packed.js
347 ms
highslide.config.js
344 ms
highslide.css
345 ms
css
27 ms
close.png
76 ms
loading.gif
75 ms
prev.png
77 ms
next.png
77 ms
Pic
172 ms
Pic
131 ms
Pic
171 ms
Pic
235 ms
Pic
255 ms
Pic
257 ms
QPic
172 ms
QPic
253 ms
QPic
254 ms
QPic
281 ms
QPic
256 ms
QPic
302 ms
QPic
394 ms
QPic
374 ms
QPic
291 ms
QPic
287 ms
QPic
328 ms
QPic
337 ms
QPic
412 ms
QPic
380 ms
QPic
376 ms
QPic
399 ms
QPic
422 ms
QPic
423 ms
QPic
467 ms
QPic
439 ms
QPic
464 ms
QPic
403 ms
QPic
433 ms
QPic
473 ms
QPic
447 ms
QPic
444 ms
WEBlogPic
537 ms
WEBlogPic
538 ms
WEBlogPic
578 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
51 ms
glyphicons-halflings-regular.woff
476 ms
fontawesome-webfont.woff
442 ms
ga.js
89 ms
quotes.png
437 ms
SigStoreLogo
438 ms
SigStoreLogo
375 ms
slick.woff
363 ms
SigStoreLogo
506 ms
SigStoreLogo
395 ms
SigStoreLogo
474 ms
SigStoreLogo
390 ms
__utm.gif
12 ms
SigStoreLogo
371 ms
SigStoreLogo
402 ms
SigStoreLogo
398 ms
Facebook.png
394 ms
Twitter.png
387 ms
LinkedIn.png
389 ms
Pinterest.png
383 ms
Pic
379 ms
adminkeys.png
344 ms
ajax-loader.gif
372 ms
iubenda.js
62 ms
roundtrip.js
33 ms
custom.png
43 ms
zoomout.cur
43 ms
loader.white.gif
42 ms
iubenda_i_badge.css
8 ms
iubenda_i_badge.js
16 ms
icon_green_mini.png
9 ms
OBIUHNQHVRG2LG5V6T6UDA
13 ms
OVTQAEAVNFBB3ODTD63XWX.js
303 ms
index.js
4 ms
makingthemark.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-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
makingthemark.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
makingthemark.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
Image elements do not have [alt] attributes
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 uses 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 Makingthemark.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 Makingthemark.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.
makingthemark.com
Open Graph description is not detected on the main page of Making The Mark. 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: