Page summary

https://www.aecdaily.com/

Tested using Chrome 94.0.4606.54 (runtime settings).

SummaryWaterfall MetricsVideoFilmstrip CoachPageXrayCPU Third party axeSustainable Web
| Summary | | Download log | Download Video | Download Timeline Log | Download HAR | 

Summary

MetricValue
Performance Score54
Total Page Transfer Size6.7 MB
Requests78
TTFB [median]385 ms
Fully Loaded [median]9.581 s
First Visual Change [median]1.419 s
First Contentful Paint (FCP) [median]1.225 s
Largest Contentful Paint (LCP) [median]2.235 s
Cumulative Layout Shift (CLS) [median]0.21
Total Blocking Time [median]257 ms
Max Potential FID [median]151 ms
CPU long tasks [median]7
CPU longest task duration151 ms
Speed Index [median]2.100 s
Visual Complete 85% [median]2.451 s
Visual Complete 99% [median]2.483 s
Last Visual Change [median]2.483 s
Screenshot of run 1

Timings Summary

Metricminmedianmeanmax
Visual Metrics
FirstVisualChange1.419 s1.419 s1.419 s1.419 s
LastVisualChange2.483 s2.483 s2.483 s2.483 s
SpeedIndex2.100 s2.100 s2.100 s2.100 s
LargestImage2.451 s2.451 s2.451 s2.451 s
LastMeaningfulPaint2.451 s2.451 s2.451 s2.451 s
VisualReadiness1.064 s1.064 s1.064 s1.064 s
VisualComplete852.451 s2.451 s2.451 s2.451 s
VisualComplete952.483 s2.483 s2.483 s2.483 s
VisualComplete992.483 s2.483 s2.483 s2.483 s
RUM Metrics
TTFB385 ms385 ms385 ms385 ms
LCP2.235 s2.235 s2.235 s2.235 s
FCP1.225 s1.225 s1.225 s1.225 s
firstPaint1.225 s1.225 s1.225 s1.225 s
loadEventEnd2.271 s2.271 s2.271 s2.271 s
CLS0.210.210.210.21
CPU
Total Blocking Time257 ms257 ms257 ms257 ms
Max Potential FID151 ms151 ms151 ms151 ms
CPU long tasks 7777
Download run logDownload videoDownload timelineDownload HAR
| Waterfall | | Download HAR | 

Waterfall

Run 1 SpeedIndex median

Choose HAR:

Download HAR
| Video | Download | 

Video

Download video
| Filmstrip | 

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s
1 sCPU Long Task duration 70 ms
1.2 sCPU Long Task duration 72 ms
1.3 sLayout Shift 0.00526 1.220 sFirst Contentful Paint 1.225 sDOM Content Loaded Time 1.244 s
1.4 sCPU Long Task duration 103 msLayout Shift 0.00132 1.397 s
1.5 sFirst Visual Change 1.419 sCPU Long Task duration 109 ms
1.6 sLayout Shift 0.18646 1.570 s
1.7 sCPU Long Task duration 82 ms
1.8 sCPU Long Task duration 62 msLayout Shift 0.01695 1.759 s
1.9 s
2 s
2.1 sCPU Long Task duration 151 ms
2.3 sLayout Shift 0.00001 2.220 sLCP <IMG> 2.235 sPage Load Time 2.267 s
2.4 s
2.5 sVisual Complete 85% 2.451 sLargest Image 2.451 sLast Visual Change 2.483 sVisual Complete 95% 2.483 sVisual Complete 99% 2.483 s
| Performance advice | Best practice advice | Privacy advice | Page info | Technologies | 

Coach

The coach helps you find performance problems on your web page using web performance best practice rules. And gives you advice on privacy and best practices.

I am the coach

Coach score

Performance advice (54)

TitleAdviceScore
Don't scale images in the browser (avoidScalingImages)The page has 17 images that are scaled more than 100 pixels. It would be better if those images are sent so the browser don't need to scale them.0
Description: It's easy to scale images in the browser and make sure they look good in different devices, however that is bad for performance! Scaling images in the browser takes extra CPU time and will hurt performance on mobile. And the user will download extra kilobytes (sometimes megabytes) of data that could be avoided. Don't do that, make sure you create multiple version of the same image server-side and serve the appropriate one.
Offenders:
Avoid slowing down the critical rendering path (fastRender)The page has 17 render blocking CSS requests and 15 blocking JavaScript requests inside of head.0
Description: The critical rendering path is what the browser needs to do to start rendering the page. Every file requested inside of the head element will postpone the rendering of the page, because the browser need to do the request. Avoid loading JavaScript synchronously inside of the head (you should not need JavaScript to render the page), request files from the same domain as the main document (to avoid DNS lookups) and inline CSS or use server push for really fast rendering and a short rendering path.
Offenders:
Inline CSS for faster first render (inlineCss)The page has both inline styles as well as it is requesting 17 CSS files inside of the head. Let's only inline CSS for really fast render.90
Description: In the early days of the Internet, inlining CSS was one of the ugliest things you can do. That has changed if you want your page to start rendering fast for your user. Always inline the critical CSS when you use HTTP/1 and HTTP/2 (avoid doing CSS requests that block rendering) and lazy load and cache the rest of the CSS. It is a little more complicated when using HTTP/2. Does your server support HTTP push? Then maybe that can help. Do you have a lot of users on a slow connection and are serving large chunks of HTML? Then it could be better to use the inline technique, becasue some servers always prioritize HTML content over CSS so the user needs to download the HTML first, before the CSS is downloaded.
Offenders:
Avoid CPU Long Tasks (longTasks)The page has 7 CPU long tasks with the total of 649 ms. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your Long Task.0
Description: Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using.
Offenders:
  • self
  • unknown
  • unknown
  • self
  • self
  • unknown
  • self
Avoid Frontend single point of failures (spof)The page has 13 requests inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head.70
Description: A page can be stopped from loading in the browser if a single JavaScript, CSS, and in some cases a font, couldn't be fetched or is loading really slowly (the white screen of death). That is a scenario you really want to avoid. Never load 3rd-party components synchronously inside of the head tag.
Offenders:
Avoid extra requests by setting cache headers (cacheHeaders)The page has 13 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 2 MB the next access.0
Description: The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request.
Offenders:
Long cache headers is good (cacheHeadersLong)The page has 58 requests that have a shorter cache time than 30 days (but still a cache time).42
Description: Setting a cache header is good. Setting a long cache header (at least 30 days) is even better beacause then it will stay long in the browser cache. But what do you do if that asset change? Rename it and the browser will pick up the new version.
Offenders:
Always compress text content (compressAssets)The page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead.90
Description: In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith.
Offenders:
Total CSS size shouldn't be too big (cssSize)The total CSS transfer size is 135.2 kB and uncompressed size is 653.8 kB. That is big and the CSS could most probably be smaller.0
Description: Delivering a massive amount of CSS to the browser is not the best thing you can do, because it means more work for the browser when parsing the CSS against the HTML and that makes the rendering slower. Try to send only the CSS that is used on that page. And make sure to remove CSS rules when they aren't used anymore.
The favicon should be small and cacheable (favicon)The favicon size is 15.1 kB bytes. That's quite big, can you make it smaller? The favicon has no cache time. 0
Description: It is easy to make the favicon big but please avoid doing that, because every browser will then perform an unnecessarily large download. And make sure the cache headers are set for a long time for the favicon. It is easy to miss since it's another content type.
Offenders:
Avoid too many fonts (fewFonts)The page has 2 font requests. Do you really need them? What value does the fonts give the user?80
Description: How many fonts do you need on a page for the user to get the message? Fonts can slow down the rendering of content, try to avoid loading too many of them because worst case it can make the text invisible until they are loaded (FOIT—flash of invisible text), best case they will flicker the text content when they arrive.
Offenders:
Total image size shouldn't be too big (imageSize)The page total image size is 5 MB. It's really big. Is the page using the right format for the images? Are they compressed as good as they can be? Make them smaller by using https://imageoptim.com/.50
Description: Avoid having too many large images on the page. The images will not affect the first paint of the page, but it will eat bandwidth for the user.
Total JavaScript size shouldn't be too big (javascriptSize)The total JavaScript transfer size is 501.9 kB and the uncompressed size is 1.3 MB. This is totally crazy! There is really room for improvement here. 0
Description: A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks?
Avoid using incorrect mime types (mimeTypes)The page has 4 misconfigured mime types. 96
Description: It's not a great idea to let browsers guess content types (content sniffing), in some cases it can actually be a security risk.
Offenders:
Make each CSS response small (optimalCssSize)https://static.aecdaily.com/fontawesome_pkgs/fontawesome-pro-6.5.2-web/css/all.min.css size is 102.5 kB (102458) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB.90
Description: Make CSS responses small to fit into the magic number TCP window size of 14.5 KB. The browser can then download the CSS faster and that will make the page start rendering earlier.
Offenders:
Total page size shouldn't be too big (pageSize)The page total transfer size is 7.1 MB, which is more than the coach limit of 2 MB. That is insane and you need to make it smaller.0
Description: Avoid having pages that have a transfer size over the wire of more than 2 MB (desktop) and 1 MB (mobile) because that is really big and will hurt performance and will make the page expensive for the user if she/he pays for the bandwidth.
Don't use private headers on static content (privateAssets)The page has 2 requests with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone.80
Description: If you set private headers on content, that means that the content are specific for that user. Static content should be able to be cached and used by everyone. Avoid setting the cache header to private.
Offenders:

Best practice advice (86)

TitleAdviceScore
Declare the language code for your document (language)The page is missing a language definition in the HTML tag. Define it with <html lang="YOUR_LANGUAGE_CODE">0
Description: According to the W3C recommendation you should declare the primary language for each Web page with the lang attribute inside the <html> tag https://www.w3.org/International/questions/qa-html-language-declarations#basics.
Cumulative Layout Shift (layoutShift)You have elements that shift. You should manually check the filmstrip or video and check if it will affect the user.79
Description: Cumulative Layout Shift measures the sum total of all individual layout shift scores for every unexpected layout shift that occurs during the entire lifespan of the page. A layout shift occurs any time a visible element changes its position from one rendered frame to the next.
Offenders:
  • P
  • DIV container12
  • DIV container12
  • DIV container12
  • DIV column12 omega
  • DIV image-frame
  • DIV image-frame
  • DIV image-frame
  • DIV image-frame
  • LI
  • LI
  • LI
  • DIV
  • LI
  • BUTTON top-nav-search-button
Avoid Unnecessary Headers (unnecessaryHeaders)There are 3 responses that sets a p3p header. There are 7 responses that sets both a max-age and expires header. There are 9 responses that sets a pragma no-cache header (that is a request header). There are 78 responses that sets a server header. 3
Description: Do not send headers that you don't need. We look for p3p, cache-control and max-age, pragma, server and x-frame-options headers. Have a look at Andrew Betts - Headers for Hackers talk as a guide https://www.youtube.com/watch?v=k92ZbrY815c or read https://www.fastly.com/blog/headers-we-dont-want.
Offenders:

Privacy advice (68)

TitleAdviceScore
Use a good Content-Security-Policy header to make sure you you avoid Cross Site Scripting (XSS) attacks. (contentSecurityPolicyHeader)Set a Content-Security-Policy header to make sure you are not open for Cross Site Scripting (XSS) attacks. You can start with setting a Content-Security-Policy-Report-Only header, that will only report the violation, not stop the download.0
Description: Content Security Policy is delivered via a HTTP response header, and defines approved sources of content that the browser may load. It can be an effective countermeasure to Cross Site Scripting (XSS) attacks and is also widely supported and usually easily deployed. https://scotthelme.co.uk/content-security-policy-an-introduction/.
Offenders:
Set a permission policy header that opt out your users being tracked in Chrome by FLoC. (disableFLoCHeader)Set a permission policy header that opt out Chrome for tracking what your users do on your site.0
Description: Googles new tracking method is called Federated Learning of Cohorts (FLoC) and it groups you based on your interests and demographics, derived from your browsing history, to enable creepy advertising and other content targeting without third-party cookies. You can avoid that by setting a Permissions-Policy header with the value of interest-cohort=(). See https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea.
Offenders:
Avoid using Google reCAPTCHA (googleReCaptcha)You share your user data with Google since you use Google reCAPTCHA.0
Description: You should avoid using Google reCAPTCHA since it will share your users information with Google.
Offenders:
Set a referrer-policy header to make sure you do not leak user information. (referrerPolicyHeader)Set a referrer-policy header to make sure you do not leak user information.0
Description: Referrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites. https://scotthelme.co.uk/a-new-security-header-referrer-policy/.
Offenders:
Set a strict transport header to make sure the user always use HTTPS. (strictTransportSecurityHeader)A strict transport header is set but miss out on setting includeSubDomainsThe max age is lower than six months. Increase it to get a better score.70
Description: The HTTP Strict-Transport-Security response header (often abbreviated as HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security.
Do not share user data with third parties. (thirdPartyPrivacy)The page has 3% requests that are 3rd party (2 requests with a size of 356.1 kB). The page also have request to companies that harvest data from users and do not respect users privacy (see https://en.wikipedia.org/wiki/Surveillance_capitalism). The page do 1 utility request and uses 1 utility tool. The page do 2 survelliance requests and uses 2 survelliance tools.0
Description: Using third party requests shares user information with that third party. Please avoid that! The project https://github.com/patrickhulce/third-party-web is used to categorize first/third party requests.
Offenders:

Page info

Page info
TitleAEC Daily - Free Continuing Education
Width1350
Height2654
DOM elements805
Avg DOM depth10
Max DOM depth13
Iframes0
Script tags29
Local storage0 b
Session storage0 b
HTML vs AMPPlain good HTML page
Resource Hints
preconnect
https://fonts.bunny.net/
https://static.aecdaily.com/

Technologies used to build the page.

Data collected using Wappalyzer.  Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyser find more information about technologies used.

TechnologyConfidenceCategory
PHP 8.1.29100  Programming languages
Apache 100  Web servers
reCAPTCHA 100  Security
jQuery 100  JavaScript libraries
OWL Carousel 100  Widgets
FancyBox 100  JavaScript libraries

Data collected using Third Party Web.

Utility
Other Google APIs/SDKs
Survelliance
Other Google APIs/SDKs
Google CDN
Cdn
Google CDN
| Browser metrics | Visual Metrics | Largest Contentful Paint | Cumulative Layout Shift | Visual Elements | Metrics from CDP | 

Visual Metrics

Visual Metrics
First Visual Change1.419 s
Speed Index2.100 s
Largest Image2.451 s
Last Meaningful Paint2.451 s
Visual Complete 85%2.451 s
Visual Complete 95%2.483 s
Visual Complete 99%2.483 s
Last Visual Change2.483 s
Visual Readiness1.064 s

Browser Metrics

Navigation Timing
backEndTime385 ms
domContentLoadedTime1.244 s
domInteractiveTime1.244 s
domainLookupTime3 ms
frontEndTime1.855 s
pageDownloadTime27 ms
pageLoadTime2.267 s
redirectionTime0 ms
serverConnectionTime39 ms
serverResponseTime342 ms
Google Web Vitals
First Contentful Paint (FCP)1.225 s
Largest Contentful Paint (LCP)2.235 s
Cumulative Layout Shift (CLS)0.21
Total Blocking Time (TBT)257 ms
Extra timings
First Contentful Paint (FCP)1.225 s
First Paint1.225 s
Largest Contentful Paint (LCP)2.235 s
Load Event End2.271 s
Fully loaded9.581 s

Largest Contentful Paint

When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.

Element typeIMG
Element/tag<img data-src="https://sizer.aecdaily.com/0x380/res/marketing_images/1059306/v5_catalyst10.png" alt="Noise Control Construction: Beyond STC and IIC" title="Noise Control Construction: Beyond STC and IIC" class="owl-lazy" src="https://sizer.aecdaily.com/0x380/res/marketing_images/1059306/v5_catalyst10.png" style="opacity: 1;">
Render time 2.235 s
Load time2.235 s
URL https://sizer.aecdai...v5_catalyst10.png
Size (width*height)315010
DOM path
div:eq(1) > div#left-container > div:eq(0) > div > div:eq(0) > div > div:eq(5) > div > img> div:eq(1) > div#left-container > div:eq(0) > div > div:eq(0) > div > div:eq(5) > div > img>
LCP

The largest contentful paint is highlighted in the image. If no element is highlighted the element was removed before the screenshot or the LCP API couldn't find the element.

The Largest Contentful Paint API highlighted this image as a part of the LCP.

LCP

Detected Cumulative Layout Shift

0.20999 cumulative layout shift collected from the Cumulative Layout Shift API.

These HTML elements contribute most to the Cumulative Layout Shifts of the page. The higher score, the more layout shift.

ScoreHTML Element
0.18646<div id="" class="column12 omega"></div>,<div class="image-frame" style="padding-top: 45.82%; height: unset;"></div>,<div class="image-frame" style="padding-top: 45.82%; height: unset;"></div>,<div class="image-frame" style="padding-top: 45.82%; height: unset;"></div>,<div class="image-frame" style="padding-top: 45.82%; height: unset;"></div>
body > div:eq(1) > div#left-container > div:eq(1),body > div:eq(1) > div#left-container > div:eq(1) > div > div > div:eq(4) > a > div > div,body > div:eq(1) > div#left-container > div:eq(1) > div > div > div:eq(5) > a > div > div,body > div:eq(1) > div#left-container > div:eq(1) > div > div > div:eq(6) > a > div > div,body > div:eq(1) > div#left-container > div:eq(1) > div > div > div:eq(7) > a > div > div
0.01695<li></li>,<li></li>,<li></li>,<div></div>,<li></li>
body > div#full-header-container > div#top-nav-container > div#top-nav > ul#menu > li:eq(5),body > div#full-header-container > div#top-nav-container > div#top-nav > ul#menu > li:eq(0),body > div#full-header-container > div#top-nav-container > div#top-nav > ul#menu > li:eq(1),body > div:eq(1) > div#left-container > div:eq(0) > div > div:eq(0) > div > div:eq(5) > div > div,body > div#full-header-container > div#top-nav-container > div#top-nav > ul#menu > li:eq(6)
0.00526<p id="tagline"></p>,<div id="top-nav-container" class="container12"></div>
body > div#full-header-container > div#full-header-container-inner > div#header > div#logo-container > p#tagline,body > div#full-header-container > div#top-nav-container
0.00132<div id="full-header-container-inner" class="container12"></div>,<div id="top-nav-container" class="container12"></div>
body > div#full-header-container > div#full-header-container-inner,body > div#full-header-container > div#top-nav-container
0.00001<button type="submit" class="top-nav-search-button" id=""></button>
body > div#full-header-container > div#full-header-container-inner > div#header > div:eq(1) > div > form#search-aec-topnav > button
Layout shift

The elements that have shifted place is highlighted in the image (that have a higher value than 0.01). If the element shifted outside of the viewport, you will not see it there. It can be hard to understand what content that has shifted, if that's the case, checkout the video or the filmstrip of the run.

Server timings

There are no Server Timings.

Custom metrics collected through JavaScript

There are no custom configured scripts.

Extra metrics collected using scripting

There are no custom extra metrics from scripting.

CDP Performance

namevalue
AudioHandlers0
Documents1
Frames1
JSEventListeners96
LayoutObjects1580
MediaKeySessions0
MediaKeys0
Nodes2091
Resources79
ContextLifecycleStateObservers3
V8PerContextDatas1
WorkerGlobalScopes0
UACSSResources0
RTCPeerConnections0
ResourceFetchers1
AdSubframes0
DetachedScriptStates0
ArrayBufferContents0
LayoutCount25
RecalcStyleCount52
LayoutDuration231
RecalcStyleDuration105
DevToolsCommandDuration49
ScriptDuration483
V8CompileDuration3
TaskDuration1792
TaskOtherDuration921
ThreadTime1
ProcessTime2
JSHeapUsedSize4600596
JSHeapTotalSize6586368
FirstMeaningfulPaint2259

Visual Elements

NameDisplay TimeX YWidthHeight
LargestImage (mkgfc_overheaddoor_ipd522_02_23.jpg)2.451 s 115 177 1120 380
<img data-src="https://sizer.aecdaily.com/0x380/edu/f2f/courses/10851/mkgfc_overheaddoor_ipd522_02_23.jpg" alt="Upward-Acting Residential Sectional Door Systems" title="Upward-Acting Residential Sectional Door Systems" class="owl-lazy" src="https://sizer.aecdaily.com/0x380/edu/f2f/courses/10851/mkgfc_overheaddoor_ipd522_02_23.jpg" style="opacity: 1;">
| Summary  | Largest responses  | Requests and sizes per content type  | Size and requests per domain  | Expires and last modified statistics  | Requests loaded after onLoad event  | Render blocking requests  | 

PageXray

How the page is built.

Summary
HTTP versionHTTP/1.1
Total requests78
Total domains9
Total transfer size6.7 MB
Total content size8.1 MB
Responses missing compression29
Number of cookies3
Third party cookies0
Requests per response code
20077
2041

Largest assets on the page (by transfer size)

URLTypeTransfer SizeContent Size
https://simages.aecd...e9c719b7fa41e.gifimage1.8 MB1.8 MB
https://sizer.aecdai.../v5_avcon02_3.pngimage865.1 KB865.1 KB
https://sizer.aecdai...etresistant01.pngimage827.4 KB827.4 KB
https://sizer.aecdai...v5_catalyst10.pngimage669.7 KB669.7 KB
https://static.aecda...duotone-900.woff2other440.5 KB440.5 KB
https://static.aecda...regular-400.woff2other411.4 KB411.4 KB
https://www.gstatic..../recaptcha__en.jsjavascript346.3 KB811.9 KB
https://static.aecda...a-solid-900.woff2other342.3 KB342.3 KB
https://static.aecda...-brands-400.woff2other116.1 KB116.1 KB
https://sizer.aecdai..._ipd522_02_23.jpgimage100.9 KB100.9 KB
https://static.aecda...b/css/all.min.csscss100.1 KB511.1 KB
https://static.aecda...aec_25yrs_www.pngimage54.5 KB54.5 KB
https://sizer.aecdai...054/v5_jain01.pngimage48.9 KB48.9 KB
https://sizer.aecdai...v5_firetrol03.pngimage42.9 KB42.9 KB
https://sizer.aecdai...v5_feeney03_3.pngimage41.8 KB41.8 KB
https://sizer.aecdai...v5_aecdaily09.pngimage41.5 KB41.5 KB
https://sizer.aecdai...6/v5_trex01_2.pngimage39.5 KB39.5 KB
https://sizer.aecdai...ativetrails03.pngimage34.1 KB34.1 KB
https://sizer.aecdai.../v5_aepspan04.pngimage33.8 KB33.8 KB
https://sizer.aecdai...zhender_03_25.pngimage32.9 KB32.9 KB

Requests and sizes per content type

ContentHeader SizeTransfer SizeContent SizeRequests
html1.3 KB13.1 KB88.4 KB4
css7.6 KB132.0 KB638.5 KB18
javascript9.5 KB490.1 KB1.3 MB24
image7.1 KB4.8 MB4.8 MB23
font0 b24.5 KB23.0 KB2
other1.2 KB1.3 MB1.3 MB4
json418 B1.0 KB930 B1
plain469 B452 B452 B1
favicon511 B14.7 KB14.7 KB1
Total28.2 KB6.7 MB8.1 MB78

Size and requests per domain

DomainHeader SizeTransfer SizeContent SizeRequests
www.aecdaily.com12.9 KB92.5 KB339.9 KB27
static.aecdaily.com5.9 KB1.5 MB2.1 MB16
fonts.bunny.netN/A25.8 KB29.2 KB3
infodata.aecdaily.com1.3 KB1.1 KB2.1 KB4
www.google.comN/A1.5 KB1.6 KB1
simages.aecdaily.com1.4 KB1.8 MB1.8 MB4
matomo.aecdaily.com528 B21.5 KB65.9 KB2
www.gstatic.comN/A346.3 KB811.9 KB1
sizer.aecdaily.com6.1 KB2.9 MB2.9 MB20

Expires and last modified statistics

typeminmedianmax
Expires0 seconds2 days1 year
Last modified3 days2 years13 years

Requests loaded after onLoad event

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript0 b0
image1.9 MB3
font0 b0
json1.0 KB1
plain452 B1
favicon14.7 KB1
Total1.9 MB6

Requests loaded after onContentLoad

Includes requests done after onLoad.

ContentTransfer SizeRequests
html90 B3
css0 b0
javascript347.0 KB3
image4.7 MB22
font0 b0
other968.0 KB3
json1.0 KB1
plain452 B1
favicon14.7 KB1
Total6.0 MB34

Render blocking requests

Render blocking information directly from Chrome.

BlockingIn body parser blockingPotentially blocking
3152

Render information

URLType
https://static.aecda...duotone-900.woff2non_blocking
https://static.aecda...regular-400.woff2non_blocking
https://www.gstatic..../recaptcha__en.jsnon_blocking
https://static.aecda...a-solid-900.woff2non_blocking
https://static.aecda...-brands-400.woff2non_blocking
https://static.aecda...b/css/all.min.cssblocking
https://static.aecda...uery-3.7.1.min.jsblocking
https://matomo.aecdaily.com/matomo.jsnon_blocking
https://www.aecdaily...query.fancybox.jsblocking
https://static.aecda...opentip-jquery.jsblocking
https://static.aecda.../flatpickr.min.jsblocking
https://fonts.bunny....-400-normal.woff2non_blocking
https://fonts.bunny....-700-normal.woff2non_blocking
https://static.aecda....1/parsley.min.jsblocking
https://www.aecdaily...l.carousel.min.jsblocking
https://static.aecda...y.validate.min.jsblocking
https://www.aecdaily...y.autocomplete.jsblocking
https://www.aecdaily...css/fluid_olc.cssblocking
https://www.aecdaily...1965/css/base.cssblocking
https://simages.aecd...ch/aecdailyjs.phppotentially_blocking
https://www.aecdaily...7840/css/menu.cssblocking
https://www.aecdaily...ookies/cookies.jsin_body_parser_blocking
https://static.aecda...flatpickr.min.cssblocking
https://www.aecdaily...uid_form_temp.cssblocking
https://www.aecdaily...cript/main_aec.jsblocking
https://www.aecdaily...9191/css/1140.cssblocking
https://static.aecda...ery.modal.min.cssblocking
https://static.aecda...uery.modal.min.jsblocking
https://www.aecdaily...uery.fancybox.cssblocking
https://www.google.com/recaptcha/api.jspotentially_blocking
https://www.aecdaily.../css/fluid_sc.cssblocking
https://fonts.bunny....nts.bunny.net/cssblocking
https://static.aecda...6/css/opentip.cssblocking
https://www.aecdaily....carousel.min.cssblocking
https://www.aecdaily...oating_goodies.jsin_body_parser_blocking
https://www.aecdaily...4/css/parsley.cssblocking
https://www.aecdaily...id_transcript.cssblocking
https://www.aecdaily...query-aecdaily.jsblocking
https://www.aecdaily...e.default.min.cssblocking
https://infodata.aec...js/postreport.phpnon_blocking
https://www.aecdaily...ddRemoveCourse.jsblocking
https://www.aecdaily...ddRemoveCourse.jsin_body_parser_blocking
https://infodata.aec.../js/abchecker.phpin_body_parser_blocking
https://www.aecdaily...ating_goodies.cssin_body_parser_blocking
https://www.aecdaily...ipt/global.js.phpblocking
https://www.aecdaily...ript/jumpToTop.jsblocking
https://static.aecda.../fa-aec-icons.cssblocking
https://infodata.aecdaily.com/js/dfp.jsnon_blocking
| CPU Long Tasks | CPU Time Spent | CPU Time Spent Per Request | CPU Time Per Tool/Domain | 

CPU

Download the Chrome trace log and drag and drop it into Developer Tools / Performance in Chrome.

Download trace log

Long Tasks

Collected using the Long Task API. A long task is a task that take 50 milliseconds or more.

TypeQuantityTotal duration (ms)
Total Blocking Time 257
Max Potential First Input Delay 151
Long Tasks before First Paint2142
Long Tasks before First Contentful Paint2142
Long Tasks after Load Event End00
Total Long Tasks7649

Individual Long Tasks

namestartTimedurationcontainerIdcontainerNamecontainerSrccontainerType
self98770window
unknown113272window
unknown1325103window
self1455109window
self163182window
unknown171462window
self2044151window

CPU time spent

Calculated using Tracium.

Categories (ms)
parseHTML125
styleLayout341
paintCompositeRender208
scriptParseCompile3
scriptEvaluation556
garbageCollection62
other508
Events (ms)
RunTask451
V8.Execute400
Layout230
CompositeLayers124
UpdateLayoutTree110
V8.RunMicrotasks109
ParseHTML96
UpdateLayerTree41
V8.GC_MC_INCREMENTAL_EMBEDDER_TRACING35
Paint35
ParseAuthorStyleSheet29
V8.GC_HEAP_EMBEDDER_TRACING_EPILOGUE20
V8.GC_MC_MARK_MAIN15
EvaluateScript13
V8.BytecodeBudgetInterrupt12

Time spent per request

URLCPU time (ms)
https://static.aecdaily.com/jquery/jquery-3.7.1.min.js320
https://www.gstatic.com/recaptcha/releases/naPR4A6FAh-yZLuCX253WaZq/recaptcha__en.js145
https://matomo.aecdaily.com/matomo.js83

CPU time spent

Tool/domainTime (ms)
static.aecdaily.com319.9
Google CDN144.8
matomo.aecdaily.com83.3
| Categories | | Tools | | First vs third | 

Third party

Third party requests categorised by Third party web.

CategoryRequests
utility 1
survelliance 2
cdn 1
CategoryNumber of tools
utility 1
survelliance 2
cdn 1

Third party requests and tools

utility (1 requests)
Other Google APIs/SDKs
survelliance (2 requests)
Other Google APIs/SDKs
Google CDN
cdn (1 requests)
Google CDN

Unmatched third party domains

Here's a list of domains that didn't match any tool in Third party web. If you are sure they are third party domains, please do a PR to that project. You can also fine tune the list using --firstParty.

fonts.bunny.net

First party requests and sizes per content type

Calculated using .*aecdaily.* (use --firstParty to configure).

ContentHeader SizeTransfer SizeContent SizeRequests
html1.3 KB13.1 KB88.4 KB4
css7.6 KB130.7 KB632.3 KB17
javascript9.5 KB142.4 KB473.5 KB22
image7.1 KB4.8 MB4.8 MB23
font0 b0 b0 b0
other1.2 KB1.3 MB1.3 MB4
json418 B1.0 KB930 B1
plain469 B452 B452 B1
favicon511 B14.7 KB14.7 KB1
Total28.2 KB6.4 MB7.3 MB73

Third party requests and sizes per content type

ContentHeader SizeTransfer SizeContent SizeRequests
html0 b0 b0 b0
css0 b1.3 KB6.2 KB1
javascript0 b347.7 KB813.4 KB2
image0 b0 b0 b0
font0 b24.5 KB23.0 KB2
TotalN/A373.5 KB842.6 KB5

Axe

Axe is an accessibility testing engine for websites and other HTML-based user interfaces. Read more about axe-core.

Violations

Median number of violations for all the runs. Check each individual run to see all the violations.

TypeViolations (median)
Critical 1
Serious2
Moderate3
Minor1

| Per domain | Dirtiest assets | Per Content Type | 

Sustainable Web

We know that using the internet means using electricity, and because most of that electricity comes from fossil fuels, it means that more data we send, the more fossil fuels we end up burning.

This is terrible news for the climate, and building a sustainable web is the 9th of the W3C's Ethical Web Principles.

If you build for the web, much of what you know about making sites faster and more accessible also makes them greener. If you're interested in learning more, you can find out at The Green Web Foundation.

Use--sustainable.pageViewsto configure the number of page views and calculate total CO2 emission.

Page viewsEstimated CO2 emissions (median)Transfer Size
1 page view total20.30 grams6.7 MB
1 page view first party19.40 grams (95.56 %)6.4 MB
1 page view third party0.90 grams (4.44 %)373.5 KB

Per domain(first run)

DomainEstimated CO2 emissionsTransfer Size
sizer.aecdaily.com 8.89 grams (43.78 %)2.9 MB
simages.aecdaily.com 5.56 grams (27.41 %)1.8 MB
static.aecdaily.com 4.60 grams (22.68 %)1.5 MB
www.gstatic.com green0.82 grams (4.05 %)346.3 KB
www.aecdaily.com 0.28 grams (1.36 %)92.5 KB
fonts.bunny.net 0.08 grams (0.38 %)25.8 KB
matomo.aecdaily.com 0.06 grams (0.31 %)21.5 KB
www.google.com green0.00 grams (0.02 %)1.5 KB
infodata.aecdaily.com 0.00 grams (0.02 %)1.1 KB

Dirtiest assets(first run)

AssetEstimated CO2 emissionsTransfer Size
https://simages.aecd...e9c719b7fa41e.gif5.55 grams (27.33 %)1.8 MB
https://sizer.aecdai.../v5_avcon02_3.png2.57 grams (12.68 %)865.1 KB
https://sizer.aecdai...etresistant01.png2.46 grams (12.13 %)827.4 KB
https://sizer.aecdai...v5_catalyst10.png1.99 grams (9.82 %)669.7 KB
https://static.aecda...duotone-900.woff21.31 grams (6.46 %)440.5 KB
https://static.aecda...regular-400.woff21.22 grams (6.03 %)411.4 KB
https://www.gstatic..../recaptcha__en.js1.03 grams (5.08 %)346.3 KB
https://static.aecda...a-solid-900.woff21.02 grams (5.02 %)342.3 KB
https://static.aecda...-brands-400.woff20.35 grams (1.70 %)116.1 KB
https://sizer.aecdai..._ipd522_02_23.jpg0.30 grams (1.48 %)100.9 KB

Per Content Type(first run)

Content TypeEstimated CO2 emissionsTransfer Size
image14.60 grams (71.91 %)4.8 MB
other3.90 grams (19.21 %)1.3 MB
javascript1.46 grams (7.19 %)490.1 KB
css0.39 grams (1.94 %)132.0 KB
font0.07 grams (0.36 %)24.5 KB
favicon0.04 grams (0.22 %)14.7 KB
html0.04 grams (0.19 %)13.1 KB
json0.00 grams (0.02 %)1.0 KB
plain0.00 grams (0.01 %)452 B