1.8 sec in total
249 ms
1.3 sec
241 ms
Welcome to 4core.media homepage info - get ready to check 4Core best content right away, or after learning these important things about 4core.media
Welcome to post-agency life | 4Core is run by agency veterans that create turn-key, digital advertising, marketing, and experiential solutions. Go forward
Visit 4core.mediaWe analyzed 4core.media page load time and found that the first response time was 249 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.
4core.media performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value16.1 s
0/100
25%
Value10.4 s
8/100
10%
Value990 ms
27/100
30%
Value0.005
100/100
15%
Value15.2 s
7/100
10%
249 ms
5 ms
42 ms
6 ms
8 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 72% of them (76 requests) were addressed to the original 4core.media, 8% (8 requests) were made to Fonts.gstatic.com and 7% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (646 ms) relates to the external source Cdn.funnelytics.io.
Page size can be reduced by 1.2 MB (44%)
2.7 MB
1.5 MB
In fact, the total size of 4core.media main page is 2.7 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. 75% 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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 124.2 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 124.2 kB or 84% of the original size.
Potential reduce by 137.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. Obviously, 4Core needs image optimization as it can save up to 137.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 457.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 457.2 kB or 48% of the original size.
Potential reduce by 442.4 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. 4core.media needs all CSS files to be minified and compressed as it can save up to 442.4 kB or 83% of the original size.
Number of requests can be reduced by 51 (55%)
93
42
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 4Core. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
4core.media
249 ms
wp-emoji-release.min.js
5 ms
css
42 ms
hg-mailchimp.css
6 ms
font-awesome.min.css
8 ms
simple-line-icons.css
4 ms
style.css
7 ms
settings.css
10 ms
style.css
9 ms
bootstrap.min.css
14 ms
template.min.css
25 ms
main.css
11 ms
znb_frontend.css
11 ms
126-layout.css
19 ms
style.css
11 ms
zn_dynamic.css
17 ms
jquery.js
37 ms
jquery-migrate.min.js
37 ms
jquery.themepunch.tools.min.js
55 ms
jquery.themepunch.revolution.min.js
55 ms
css
51 ms
platform.js
380 ms
style.min.css
47 ms
hg-mailchimp.js
47 ms
main.js
48 ms
plugins.min.js
48 ms
scrollmagic.js
46 ms
znscript.min.js
47 ms
SmoothScroll.min.js
128 ms
typed.min.js
129 ms
script.js
130 ms
beforeafter.min.js
129 ms
slick.min.js
127 ms
main.js
128 ms
znpb_frontend.bundle.js
137 ms
jquery.countTo.min.js
137 ms
app.js
136 ms
wp-embed.min.js
136 ms
custom-pagination.js
136 ms
track.js
646 ms
sdk.js
365 ms
submark-3.png
315 ms
dummy.png
331 ms
google-partner-RGB-mobile-400x221_c.png
334 ms
Bing-Ads-Logo.png
331 ms
Facebook-Woodmark-Logo.jpg
334 ms
Glassview-Logo.jpg
334 ms
Ads_logo_horizontal.png
333 ms
Instagram-Word-Logo.png
337 ms
1280px-LinkedIn_Logo.svg.png
337 ms
Simpli.fi-Logo.jpg
337 ms
SITO-Mobile-Logo.jpg
336 ms
StackAdapt-Logo.jpg
337 ms
AdBeat-Logo.jpg
336 ms
Alexa-Logo.png
359 ms
Asana-Logo-Horizontal-Color.png
360 ms
Moz-Logo.png
359 ms
semrush-logo-800.png
359 ms
SEOProfiler-Logo.png
359 ms
swydo.png
358 ms
Think-with-Google-Logo-Large.jpg
384 ms
Unbounce-Primary-Logo-Light-Background.png
358 ms
0.jpg
358 ms
VA.png
383 ms
sound-grey.png
358 ms
maast-grey.png
279 ms
tri-state.png
300 ms
D18.png
301 ms
kong-off.png
300 ms
RAD-Cross-Logo-Website.png
300 ms
revolution.extension.slideanims.min.js
116 ms
revolution.extension.actions.min.js
112 ms
revolution.extension.layeranimation.min.js
220 ms
revolution.extension.navigation.min.js
112 ms
revolution.extension.parallax.min.js
109 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
54 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
92 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
98 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
98 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
98 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
98 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
97 ms
glyphicons_halflingsregular.woff
97 ms
icomoon.woff
101 ms
kl-social-icons.woff
201 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
101 ms
cb=gapi.loaded_0
168 ms
cb=gapi.loaded_1
168 ms
badge.html
167 ms
sdk.js
51 ms
129 ms
print.css
72 ms
badge.css
76 ms
api.js
75 ms
badge_compiled.js
118 ms
analytics.js
128 ms
postmessageRelay
144 ms
css
64 ms
THOUGHT-LEADERSHIP-Mountain.jpg
31 ms
lg-wt.png
7 ms
cb=gapi.loaded_0
11 ms
1005847222-postmessagerelay.js
25 ms
rpc:shindig_random.js
8 ms
proxy.html
148 ms
cb=gapi.loaded_0
8 ms
googlelogo_color_150x54dp.png
17 ms
4core.media 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
4core.media 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
4core.media SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 4core.media 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 4core.media 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.
4core.media
Open Graph data is detected on the main page of 4Core. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: